Multiple Active Bandwidth Parts

ABSTRACT

Bandwidth parts (BWPs) and other resources for wireless communications are described. A wireless device may use a BWP control procedure and/or a BWP timer management procedure for activating, deactivating, and/or switching BWPs, for example, using multiple active BWPs. A base station may send information comprising one or more fields indicating an action associated with a BWP, for example, if multiple active BWPs are supported. A wireless device may control a first BWP inactivity timer associated with a first active BWP, for example, based on activating, deactivating, and/or switching a second BWP.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/414,344, filed on May 16, 2019, which is a continuation of U.S.application Ser. No. 16/413,128, filed on May 15, 2019 and now U.S. Pat.No. 10,880,949, which claims priority from and the benefit of U.S.Provisional Application No. 62/671,732, titled “Multiple ActiveBandwidth Parts” and filed on May 15, 2018, and U.S. ProvisionalApplication No. 62/672,096, titled “Bandwidth Part Inactivity TimerManagement with Multiple Active Bandwidth Parts” and filed on May 16,2018. Each of the above-referenced applications is hereby incorporatedby reference in its entirety.

BACKGROUND

Wireless communications may use bandwidth parts (BWPs) and otherwireless resources. A base station and/or a wireless device mayactivate, deactivate, and/or switch a BWP. A wireless device may not beable to determine whether downlink control information (DCI) is forswitching a BWP, activating a new BWP, or deactivating an active BWP,for example, if multiple active BWPs are supported. Misalignment mayoccur between a base station and a wireless device, for example, basedon BWP activation, deactivation, and/or switching. Signaling overheadmay increase and/or spectral efficiency may decrease, for example, as aresult of a misalignment between a base station and a wireless device.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

BWP control procedures and BWP timer management procedures aredescribed. A base station may send one or more messages to configuremultiple BWPs. The base station may configure multiple BWPs as multipleactive BWPs. The base station may send an indication of an actionassociated with a BWP. The indication may be included in DCI and/or amedia access control control element (MAC CE) that may be configured tocontrol changes for BWPs, for example, if multiple active BWPs areconfigured. A wireless device may deactivate a second active BWP, forexample, based on a first active BWP switching to a default BWP. Awireless device may restart and/or start a first BWP inactivity timer,for example, based on activating, deactivating, and/or switching asecond BWP. By providing an indication of an action associated with aBWP, and/or by performing a predetermined action based on a BWPactivation, deactivation, and/or switching, improved communicationsbetween devices may be achieved, such as reduced and/or avoidedmisalignment between a wireless device and a base station.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16A, FIG. 16B and FIG. 16C show examples of MAC subheaders.

FIG. 17A and FIG. 17B show examples of MAC PDUs.

FIG. 18 shows an example of LCIDs for DL-SCH.

FIG. 19 shows an example of LCIDs for UL-SCH.

FIG. 20A and FIG. 20B show examples of SCell Activation/Deactivation MACCE.

FIG. 21 shows an example of BWP operation.

FIG. 22 shows an example of BWP operation in an SCell.

FIG. 23A, FIG. 23B and FIG. 23C show examples of multiple active BWPsoperation.

FIG. 24A and FIG. 24B show examples of BWP scheduling.

FIG. 25A, FIG. 25B, FIG. 25C and FIG. 25D show examples of multipleactive BWPs operation.

FIG. 26A, FIG. 26B, and FIG. 26C show examples of multiple active BWPsoperation.

FIG. 27A, FIG. 27B, FIG. 27C, and FIG. 27D show examples of a MAC CE anda corresponding MAC subheader for BWP activation/deactivation.

FIG. 28A and FIG. 28B show examples of one or more fields of DCI formultiple active BWP operation indication.

FIG. 29A and FIG. 29B show examples of one or more fields of DCI formultiple active BWP operation indication.

FIG. 30A and FIG. 30B show examples of one or more fields of DCI formultiple active BWP operation indication.

FIG. 31 shows an example of a flow chart of multiple active BWPoperation.

FIG. 32 shows an example of a procedure at a cell that may be configuredwith a plurality of BWPs.

FIG. 33 shows an example method that may be performed by a wirelessdevice to configure a plurality of BWPs.

FIG. 34 shows an example method that may be performed by a base stationto configure a plurality of BWPs.

FIG. 35 shows an example of a procedure at a cell that may be configuredwith a plurality of BWPs.

FIG. 36 shows an example of a procedure at a cell that may be configuredwith a plurality of BWPs.

FIG. 37 shows an example method of configuring multiple active BWPoperation.

FIG. 38 shows an example of BWP management comprising BWP deactivationof a secondary BWP in a cell.

FIG. 39 shows an example of BWP management using multiple BWPs in acell.

FIG. 40 shows an example of BWP management with multiple BWPs in a cell.

FIG. 41 shows an example of BWP management with a primary BWP andmultiple secondary BWPs in a cell.

FIG. 42 shows an example of BWP management using cross-BWP schedulingfor multiple BWPs in a cell.

FIG. 43 shows an example of BWP management using cross-BWP schedulingfor multiple BWPs in a cell.

FIG. 44 shows an example of BWP management for multiple active BWPs in acell using BWP switching.

FIG. 45 shows an example of BWP management using a primary BWP, defaultBWP, and at least a secondary BWP in a cell.

FIG. 46 shows an example of BWP management using a primary BWP, defaultBWP, and at least a secondary BWP in a cell.

FIG. 47 shows an example of BWP management with multiple active BWPs ina cell.

FIG. 48 shows an example of BWP management with multiple active BWPs ina cell.

FIG. 49 shows an example method for BWP management by a wireless device.

FIG. 50 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto multiple active bandwidth parts in multicarrier communicationsystems.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

-   3GPP 3rd Generation Partnership Project-   5GC 5G Core Network-   ACK Acknowledgement-   AMF Access and Mobility Management Function-   ARQ Automatic Repeat Request-   AS Access Stratum-   ASIC Application-Specific Integrated Circuit-   BA Bandwidth Adaptation-   BCCH Broadcast Control Channel-   BCH Broadcast Channel-   BPSK Binary Phase Shift Keying-   BWP Bandwidth Part-   CA Carrier Aggregation-   CC Component Carrier-   CCCH Common Control CHannel-   CDMA Code Division Multiple Access-   CN Core Network-   CP Cyclic Prefix-   CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex-   C-RNTI Cell-Radio Network Temporary Identifier-   CS Configured Scheduling-   CSI Channel State Information-   CSI-RS Channel State Information-Reference Signal-   CQI Channel Quality Indicator-   CSS Common Search Space-   CU Central Unit-   DC Dual Connectivity-   DCCH Dedicated Control Channel-   DCI Downlink Control Information-   DL Downlink-   DL-SCH Downlink Shared CHannel-   DM-RS DeModulation Reference Signal-   DRB Data Radio Bearer-   DRX Discontinuous Reception-   DTCH Dedicated Traffic Channel-   DU Distributed Unit-   EPC Evolved Packet Core-   E-UTRA Evolved UMTS Terrestrial Radio Access-   E-UTRAN Evolved-Universal Terrestrial Radio Access Network-   FDD Frequency Division Duplex-   FPGA Field Programmable Gate Arrays-   F1-C F1-Control plane-   F1-U F1-User plane-   gNB next generation Node B-   HARQ Hybrid Automatic Repeat reQuest-   HDL Hardware Description Languages-   IE Information Element-   IP Internet Protocol-   LCID Logical Channel Identifier-   LTE Long Term Evolution-   MAC Media Access Control-   MCG Master Cell Group-   MCS Modulation and Coding Scheme-   MeNB Master evolved Node B-   MIB Master Information Block-   MME Mobility Management Entity-   MN Master Node-   NACK Negative Acknowledgement-   NAS Non-Access Stratum-   NG CP Next Generation Control Plane-   NGC Next Generation Core-   NG-C NG-Control plane-   ng-eNB next generation evolved Node B-   NG-U NG-User plane-   NR New Radio-   NR MAC New Radio MAC-   NR PDCP New Radio PDCP-   NR PHY New Radio PHYsical-   NR RLC New Radio RLC-   NR RRC New Radio RRC-   NSSAI Network Slice Selection Assistance Information-   O&M Operation and Maintenance-   OFDM Orthogonal Frequency Division Multiplexing-   PBCH Physical Broadcast CHannel-   PCC Primary Component Carrier-   PCCH Paging Control CHannel-   PCell Primary Cell-   PCH Paging CHannel-   PDCCH Physical Downlink Control CHannel-   PDCP Packet Data Convergence Protocol-   PDSCH Physical Downlink Shared CHannel-   PDU Protocol Data Unit-   PHICH Physical HARQ Indicator CHannel-   PHY PHYsical-   PLMN Public Land Mobile Network-   PMI Precoding Matrix Indicator-   PRACH Physical Random Access CHannel-   PRB Physical Resource Block-   PSCell Primary Secondary Cell-   PSS Primary Synchronization Signal-   pTAG primary Timing Advance Group-   PT-RS Phase Tracking Reference Signal-   PUCCH Physical Uplink Control CHannel-   PUSCH Physical Uplink Shared CHannel-   QAM Quadrature Amplitude Modulation-   QFI Quality of Service Indicator-   QoS Quality of Service-   QPSK Quadrature Phase Shift Keying-   RA Random Access-   RACH Random Access CHannel-   RAN Radio Access Network-   RAT Radio Access Technology-   RA-RNTI Random Access-Radio Network Temporary Identifier-   RB Resource Blocks-   RBG Resource Block Groups-   RI Rank indicator-   RLC Radio Link Control-   RRC Radio Resource Control-   RS Reference Signal-   RSRP Reference Signal Received Power-   SCC Secondary Component Carrier-   SCell Secondary Cell-   SCG Secondary Cell Group-   SC-FDMA Single Carrier-Frequency Division Multiple Access-   SDAP Service Data Adaptation Protocol-   SDU Service Data Unit-   SeNB Secondary evolved Node B-   SFN System Frame Number-   S-GW Serving GateWay-   SI System Information-   SIB System Information Block-   SMF Session Management Function-   SN Secondary Node-   SpCell Special Cell-   SRB Signaling Radio Bearer-   SRS Sounding Reference Signal-   SS Synchronization Signal-   SSS Secondary Synchronization Signal-   sTAG secondary Timing Advance Group-   TA Timing Advance-   TAG Timing Advance Group-   TAI Tracking Area Identifier-   TAT Time Alignment Timer-   TB Transport Block-   TC-RNTI Temporary Cell-Radio Network Temporary Identifier-   TDD Time Division Duplex-   TDMA Time Division Multiple Access-   TTI Transmission Time Interval-   UCI Uplink Control Information-   UE User Equipment-   UL Uplink-   UL-SCH Uplink Shared CHannel-   UPF User Plane Function-   UPGW User Plane Gateway-   VHDL VHSIC Hardware Description Language-   Xn-C Xn-Control plane-   Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, 1024-QAM and/or the like. Physical radio transmission may beenhanced by dynamically or semi-dynamically changing the modulation andcoding scheme, for example, depending on transmission requirementsand/or radio conditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface. The wirelessdevices 110A and/or 110B may be structurally similar to wireless devicesshown in and/or described in connection with other drawing figures. TheNode B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120Dmay be structurally similar to Nodes B and/or base stations shown inand/or described in connection with other drawing figures.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Media Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. Mapping restrictions in alogical channel prioritization may control which numerology and/ortransmission timing a logical channel may use. An RLC sublayer maysupport transparent mode (TM), unacknowledged mode (UM), and/oracknowledged mode (AM) transmission modes. The RLC configuration may beper logical channel with no dependency on numerologies and/orTransmission Time Interval (TTI) durations. Automatic Repeat Request(ARQ) may operate on any of the numerologies and/or TTI durations withwhich the logical channel is configured. Services and functions of thePDCP layer for the user plane may comprise, for example, sequencenumbering, header compression and decompression, transfer of user data,reordering and duplicate detection, PDCP PDU routing (e.g., such as forsplit bearers), retransmission of PDCP SDUs, ciphering, deciphering andintegrity protection, PDCP SDU discard, PDCP re-establishment and datarecovery for RLC AM, and/or duplication of PDCP PDUs. Services and/orfunctions of SDAP may comprise, for example, mapping between a QoS flowand a data radio bearer. Services and/or functions of SDAP may comprisemapping a Quality of Service Indicator (QFI) in DL and UL packets. Aprotocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCID for alogical channel and/or MAC CE may be configured for the wireless deviceby the base station. The MAC sub-header corresponding to a MAC CE and/ora MAC SDU may comprise an LCID associated with the MAC CE and/or the MACSDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MAC CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs indicating one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by 5GC; paging for mobile terminateddata area managed by 5GC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterInformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signalling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A, FIG. 7B,FIG. 8, and associated text, described below.

Other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be less than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SS/PBCH blocks, forexample, if the downlink CSI-RS 522 and SS/PBCH blocks are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are outside of the PRBs configured for the SS/PBCH blocks.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time for acarrier. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers (such as forcarrier aggregation) or ranging from 1 to 64 carriers (such as for dualconnectivity). Different radio frame structures may be supported (e.g.,for FDD and/or for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. Radio frame duration may be 10 milliseconds (ms). A 10 msradio frame 601 may be divided into ten equally sized subframes 602,each with a 1 ms duration. Subframe(s) may comprise one or more slots(e.g., slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Other subframe durations such as, for example, 0.5 ms, 1 ms, 2ms, and 5 ms may be supported. Uplink and downlink transmissions may beseparated in the frequency domain. Slot(s) may include a plurality ofOFDM symbols 604. The number of OFDM symbols 604 in a slot 605 maydepend on the cyclic prefix length. A slot may be 14 OFDM symbols forthe same subcarrier spacing of up to 480 kHz with normal CP. A slot maybe 12 OFDM symbols for the same subcarrier spacing of 60 kHz withextended CP. A slot may comprise downlink, uplink, and/or a downlinkpart and an uplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHaddressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CSresources. The DCI may comprise parameters indicating that the downlinkgrant is a CS grant. The CS grant may be implicitly reused according tothe periodicity defined by the one or more RRC messages. The CS grantmay be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) DCI via a PDCCH addressed to a CS-RNTI to activatethe CS resources. The DCI may comprise parameters indicating that theuplink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC message, TheCS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more transport blocks. TheDCI may indicate a downlink assignment indicating parameters forreceiving one or more transport blocks. The DCI may be used by the basestation to initiate a contention-free random access at the wirelessdevice. The base station may send (e.g., transmit) DCI comprising a slotformat indicator (SFI) indicating a slot format. The base station maysend (e.g., transmit) DCI comprising a preemption indication indicatingthe PRB(s) and/or OFDM symbol(s) in which a wireless device may assumeno transmission is intended for the wireless device. The base stationmay send (e.g., transmit) DCI for group power control of the PUCCH, thePUSCH, and/or an SRS. DCI may correspond to an RNTI. The wireless devicemay obtain an RNTI after or in response to completing the initial access(e.g., C-RNTI). The base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI, etc.). The wireless device may determine (e.g., compute)an RNTI (e.g., the wireless device may determine the RA-RNTI based onresources used for transmission of a preamble). An RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). The wireless device maymonitor a group common search space which may be used by the basestation for sending (e.g., transmitting) DCIs that are intended for agroup of wireless devices. A group common DCI may correspond to an RNTIwhich is commonly configured for a group of wireless devices. Thewireless device may monitor a wireless device-specific search space. Awireless device specific DCI may correspond to an RNTI configured forthe wireless device.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel. Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP. BWPs are describedas example resources. Any wireless resource may be applicable to one ormore procedures described herein.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a wireless device is configured with a secondary carrier on a primarycell, the wireless device may be configured with an initial BWP forrandom access procedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base station may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may not configure awireless device without a common search space on a PCell, or on aPSCell, in an active DL BWP. For an UL BWP in a set of one or more ULBWPs, a base station may configure a wireless device with one or moreresource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided with a default DL BWP, a default BWP may be aninitial active DL BWP. A default BWP may not be configured for one ormore wireless devices. A first (or initial) BWP may serve as a defaultBWP, for example, if a default BWP is not configured.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. 10 shows an example of three BWPs configured, BWP1(1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be de-activated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice. A master base station may determine (e.g., based on receivedmeasurement reports, traffic conditions, and/or bearer types) to requesta secondary base station to provide additional resources (e.g., servingcells) for a wireless device. After or upon receiving a request from amaster base station, a secondary base station may create and/or modify acontainer that may result in a configuration of additional serving cellsfor a wireless device (or decide that the secondary base station has noresource available to do so). For a wireless device capabilitycoordination, a master base station may provide (e.g., all or a part of)an AS configuration and wireless device capabilities to a secondary basestation. A master base station and a secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried via Xn messages. Asecondary base station may initiate a reconfiguration of the secondarybase station existing serving cells (e.g., PUCCH towards the secondarybase station). A secondary base station may decide which cell is aPSCell within a SCG. A master base station may or may not change contentof RRC configurations provided by a secondary base station. A masterbase station may provide recent (and/or the latest) measurement resultsfor SCG cell(s), for example, if an SCG addition and/or an SCG SCelladdition occurs. A master base station and secondary base stations mayreceive information of SFN and/or subframe offset of each other from anOAM and/or via an Xn interface (e.g., for a purpose of DRX alignmentand/or identification of a measurement gap). Dedicated RRC signaling maybe used for sending required system information of a cell as for CA, forexample, if adding a new SCG SCell, except for an SFN acquired from anMIB of a PSCell of a SCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a MAC entity, and/or a beam failure indication may initiate arandom access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating an equivalent and/orsimilar contents of Msg 1 1220 and Msg3 1240 of a four-step randomaccess procedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for a beam failurerecovery procedure and corresponding PRACH resource(s) (e.g., if any), atime window to monitor RA response(s), a time window to monitorresponse(s) on a beam failure recovery procedure, and/or a contentionresolution timer.

The Msg 1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for a beam failurerecovery procedure associated with at least one of SS blocks and/orCSI-RSs. A wireless device may select a random access preamble indexcorresponding to a selected SS block or a CSI-RS from a set of one ormore random access preambles for a beam failure recovery procedure, forexample, if at least one of the SS blocks with an RSRP above a firstRSRP threshold amongst associated SS blocks is available, and/or if atleast one of CSI-RSs with a RSRP above a second RSRP threshold amongstassociated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. The wireless device may select a random access preambleindex, for example, if a base station does not configure a wirelessdevice with at least one contention free PRACH resource associated withSS blocks or CSI-RS. The wireless device may select the at least one SSblock and/or select a random access preamble corresponding to the atleast one SS block, for example, if a base station configures thewireless device with one or more contention free PRACH resourcesassociated with SS blocks and/or if at least one SS block with a RSRPabove a first RSRP threshold amongst associated SS blocks is available.The wireless device may select the at least one CSI-RS and/or select arandom access preamble corresponding to the at least one CSI-RS, forexample, if a base station configures a wireless device with one or morecontention free PRACH resources associated with CSI-RSs and/or if atleast one CSI-RS with a RSRP above a second RSPR threshold amongst theassociated CSI-RSs is available.

A wireless device may perform one or more Msg 1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected SS block, for example,if the wireless device selects an SS block and is configured with anassociation between one or more PRACH occasions and/or one or more SSblocks. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected CSI-RS, for example, ifthe wireless device selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs.The wireless device may send (e.g., transmit), to a base station, aselected random access preamble via a selected PRACH occasions. Thewireless device may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedrandom access preamble is sent (e.g., transmitted). The wireless devicemay not determine an RA-RNTI for a beam failure recovery procedure. Thewireless device may determine an RA-RNTI at least based on an index of afirst OFDM symbol, an index of a first slot of a selected PRACHoccasions, and/or an uplink carrier index for a transmission of Msg 11220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230. The wireless device may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For a beamfailure recovery procedure, the base station may configure the wirelessdevice with a different time window (e.g., bfr-ResponseWindow) tomonitor response to on a beam failure recovery request. The wirelessdevice may start a time window (e.g., ra-ResponseWindow orbfr-ResponseWindow) at a start of a first PDCCH occasion, for example,after a fixed duration of one or more symbols from an end of a preambletransmission. If the wireless device sends (e.g., transmits) multiplepreambles, the wireless device may start a time window at a start of afirst PDCCH occasion after a fixed duration of one or more symbols froman end of a first preamble transmission. The wireless device may monitora PDCCH of a cell for at least one random access response identified bya RA-RNTI, or for at least one response to a beam failure recoveryrequest identified by a C-RNTI, at a time that a timer for a time windowis running.

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention free random accessprocedure is triggered for a beam failure recovery request and if aPDCCH transmission is addressed to a C-RNTI. The wireless device maydetermine that the random access procedure is successfully completed,and may indicate a reception of an acknowledgement for a systeminformation request to upper layers, for example, if at least one randomaccess response comprises a random access preamble identifier. Thewireless device may stop sending (e.g., transmitting) remainingpreambles (if any) after or in response to a successful reception of acorresponding random access response, for example, if the wirelessdevice has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel. A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of a MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-)Multiplexing1352 and/or (De-)Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-)Multiplexing 1352 and/or (De-)Multiplexing 1362) of MAC SDUsto one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). A MACentity may handle a random access process (e.g., Random Access Control1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4-stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station).

A base station may communicate with a wireless device via a wirelessnetwork using one or more technologies, such as new radio technologies(e.g., NR, 5G, etc.). The one or more radio technologies may comprise atleast one of: multiple technologies related to physical layer; multipletechnologies related to medium access control layer; and/or multipletechnologies related to radio resource control layer Enhancing the oneor more radio technologies may improve performance of a wirelessnetwork. System throughput, and/or data rate of transmission, may beincreased. Battery consumption of a wireless device may be reduced.Latency of data transmission between a base station and a wirelessdevice may be improved. Network coverage of a wireless network may beimproved. Transmission efficiency of a wireless network may be improved.

A base station may send (e.g., transmit) DCI via a PDCCH for at leastone of: a scheduling assignment and/or grant; a slot formatnotification; a preemption indication; and/or a power-control commandThe DCI may comprise at least one of: an identifier of a DCI format; adownlink scheduling assignment(s); an uplink scheduling grant(s); a slotformat indicator; a preemption indication; a power-control forPUCCH/PUSCH; and/or a power-control for SRS.

A downlink scheduling assignment DCI may comprise parameters indicatingat least one of: an identifier of a DCI format; a PDSCH resourceindication; a transport format; HARQ information; control informationrelated to multiple antenna schemes; and/or a command for power controlof the PUCCH. An uplink scheduling grant DCI may comprise parametersindicating at least one of: an identifier of a DCI format; a PUSCHresource indication; a transport format; HARQ related information;and/or a power control command of the PUSCH.

Different types of control information may correspond to different DCImessage sizes. Supporting multiple beams, spatial multiplexing in thespatial domain, and/or noncontiguous allocation of RBs in the frequencydomain, may require a larger scheduling message, in comparison with anuplink grant allowing for frequency-contiguous allocation. DCI may becategorized into different DCI formats. A DCI format may correspond to acertain message size and/or usage.

A wireless device may monitor (e.g., in common search space or wirelessdevice-specific search space) one or more PDCCH for detecting one ormore DCI with one or more DCI format. A wireless device may monitor aPDCCH with a limited set of DCI formats, for example, which may reducepower consumption. The more DCI formats that are to be detected, themore power may be consumed by the wireless device.

The information in the DCI formats for downlink scheduling may compriseat least one of: an identifier of a DCI format; a carrier indicator; anRB allocation; a time resource allocation; a bandwidth part indicator; aHARQ process number; one or more MCS; one or more NDI; one or more RV;MIMO related information; a downlink assignment index (DAI); a TPC forPUCCH; an SRS request; and/or padding (e.g., if necessary). The MIMOrelated information may comprise at least one of: a PMI; precodinginformation; a transport block swap flag; a power offset between PDSCHand a reference signal; a reference-signal scrambling sequence; a numberof layers; antenna ports for the transmission; and/or a transmissionconfiguration indication (TCI).

The information in the DCI formats used for uplink scheduling maycomprise at least one of: an identifier of a DCI format; a carrierindicator; a bandwidth part indication; a resource allocation type; anRB allocation; a time resource allocation; an MCS; an NDI; a phaserotation of the uplink DMRS; precoding information; a CSI request; anSRS request; an uplink index/DAI; a TPC for PUSCH; and/or padding (e.g.,if necessary).

A base station may perform CRC scrambling for DCI, for example, beforetransmitting the DCI via a PDCCH. The base station may perform CRCscrambling by binarily adding multiple bits of at least one wirelessdevice identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, SP CSI C-RNTI, and/or TPC-SRS-RNTI) on the CRC bits ofthe DCI. The wireless device may check the CRC bits of the DCI, forexample, if detecting the DCI. The wireless device may receive the DCI,for example, if the CRC is scrambled by a sequence of bits that is thesame as the at least one wireless device identifier.

A base station may send (e.g., transmit) one or more PDCCH in differentCORESETs, for example, to support a wide bandwidth operation. A basestation may transmit one or more RRC messages comprising configurationparameters of one or more CORESETs. A CORESET may comprise at least oneof: a first OFDM symbol; a number of consecutive OFDM symbols; a set ofresource blocks; and/or a CCE-to-REG mapping. A base station may send(e.g., transmit) a PDCCH in a dedicated CORESET for particular purpose,for example, for beam failure recovery confirmation. A wireless devicemay monitor a PDCCH for detecting DCI in one or more configuredCORESETs, for example, to reduce the power consumption.

A base station may send (e.g., transmit) one or more MAC PDUs to awireless device. A MAC PDU may comprise a bit string that may be bytealigned (e.g., multiple of eight bits) in length. Bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. The bit string may be readfrom the left to right, and then, in the reading order of the lines. Thebit order of a parameter field within a MAC PDU may be represented withthe first and most significant bit in the leftmost bit, and with thelast and least significant bit in the rightmost bit.

A MAC SDU may comprise a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC SDU may be included in a MAC PDU, forexample, from the first bit onward. In an example, a MAC CE may be a bitstring that is byte aligned (e.g., multiple of eight bits) in length. AMAC subheader may be a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC subheader may be placed immediately infront of the corresponding MAC SDU, MAC CE, and/or padding. A MAC entitymay ignore a value of reserved bits in a DL MAC PDU.

A MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the oneor more MAC subPDUs may comprise at least one of: a MAC subheader only(e.g., including padding); a MAC subheader and a MAC SDU; a MACsubheader and a MAC CE; and/or a MAC subheader and padding. The MAC SDUmay be of variable size. A MAC subheader may correspond to a MAC SDU, aMAC CE, and/or padding.

A MAC subheader may comprise: an R field comprising one bit; an F fieldwith one bit in length; an LCID field with multiple bits in length; an Lfield with multiple bits in length, for example, if the MAC subheadercorresponds to a MAC SDU, a variable-sized MAC CE, and/or padding.

FIG. 16A shows an example of a MAC subheader comprising an eight-bit Lfield. The LCID field may have six bits in length. The L field may haveeight bits in length.

FIG. 16B shows an example of a MAC subheader with a sixteen-bit L field.The LCID field may have six bits in length. The L field may have sixteenbits in length. A MAC subheader may comprise: a R field comprising twobits in length; and an LCID field comprising multiple bits in length(e.g., if the MAC subheader corresponds to a fixed sized MAC CE), and/orpadding.

FIG. 16C shows an example of the MAC subheader. The LCID field maycomprise six bits in length, and the R field may comprise two bits inlength.

FIG. 17A shows an example of a DL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising MAC CE may be placed before anyMAC subPDU comprising a MAC SDU, and/or before a MAC subPDU comprisingpadding.

FIG. 17B shows an example of a UL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising a MAC CE may be placed afterall MAC subPDU comprising a MAC SDU. The MAC subPDU may be placed beforea MAC subPDU comprising padding.

FIG. 18 shows first examples of LCIDs. FIG. 19 shows second examples ofLCIDs. In each of FIG. 18 and FIG. 19, the left columns compriseindices, and the right columns comprises corresponding LCID values foreach index.

FIG. 18 shows an example of an LCID that may be associated with the oneor more MAC CEs. A MAC entity of a base station may send (e.g.,transmit) to a MAC entity of a wireless device one or more MAC CEs. Theone or more MAC CEs may comprise at least one of: an SP ZP CSI-RSResource Set Activation/Deactivation MAC CE; a PUCCH spatial relationActivation/Deactivation MAC CE; a SP SRS Activation/Deactivation MAC CE;a SP CSI reporting on PUCCH Activation/Deactivation MAC CE; a TCI StateIndication for UE-specific PDCCH MAC CE; a TCI State Indication forUE-specific PDSCH MAC CE; an Aperiodic CSI Trigger State SubselectionMAC CE; a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE;a wireless device (e.g., UE) contention resolution identity MAC CE; atiming advance command MAC CE; a DRX command MAC CE; a long DRX commandMAC CE; an SCell activation and/or deactivation MAC CE (e.g., 1 Octet);an SCell activation and/or deactivation MAC CE (e.g., 4 Octet); and/or aduplication activation and/or deactivation MAC CE. A MAC CE may comprisean LCID in the corresponding MAC subheader. Different MAC CEs may havedifferent LCID in the corresponding MAC subheader. An LCID with 111011in a MAC subheader may indicate a MAC CE associated with the MACsubheader is a long DRX command MAC CE.

FIG. 19 shows further examples of LCIDs associated with one or more MACCEs. The MAC entity of the wireless device may send (e.g., transmit), tothe MAC entity of the base station, one or more MAC CEs. The one or moreMAC CEs may comprise at least one of: a short buffer status report (BSR)MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grantconfirmation MAC CE; a single entry power headroom report (PHR) MAC CE;a multiple entry PHR MAC CE; a short truncated BSR; and/or a longtruncated BSR. A MAC CE may comprise an LCID in the corresponding MACsubheader. Different MAC CEs may have different LCIDs in thecorresponding MAC subheader. The LCID with 111011 in a MAC subheader mayindicate a MAC CE associated with the MAC subheader is a short-truncatedcommand MAC CE.

Two or more component carriers (CCs) may be aggregated, for example, ina carrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit on one or more CCs, for example, depending oncapabilities of the wireless device. The CA may be supported forcontiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, forexample, if configured with CA. At (e.g., during) an RRC connectionestablishment, re-establishment and/or handover, a cell providing a NASmobility information may be a serving cell. At (e.g., during) an RRCconnection re-establishment and/or handover procedure, a cell providinga security input may be a serving cell. The serving cell may be referredto as a primary cell (PCell). A base station may send (e.g., transmit),to a wireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells), forexample, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/ordeactivation mechanism of an SCell for an efficient battery consumption,for example, if the base station and/or the wireless device isconfigured with CA. A base station may activate or deactivate at leastone of the one or more SCells, for example, if the wireless device isconfigured with one or more SCells. The SCell may be deactivated, forexample, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example,after or in response to receiving an SCell activation and/ordeactivation MAC CE. A base station may send (e.g., transmit), to awireless device, one or more messages comprising ansCellDeactivationTimer timer. The wireless device may deactivate anSCell, for example, after or in response to an expiry of thesCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell activation/deactivation MAC CE activating anSCell. The wireless device may perform operations (e.g., after or inresponse to the activating the SCell) that may comprise: SRStransmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for theSCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring forthe SCell on the PCell; and/or PUCCH transmissions on the SCell.

The wireless device may start and/or restart a timer (e.g., ansCellDeactivationTimer timer) associated with the SCell, for example,after or in response to activating the SCell. The wireless device maystart the timer (e.g., sCellDeactivationTimer timer) in the slot, forexample, if the SCell activation/deactivation MAC CE has been received.The wireless device may initialize and/or re-initialize one or moresuspended configured uplink grants of a configured grant Type 1associated with the SCell according to a stored configuration, forexample, after or in response to activating the SCell. The wirelessdevice may trigger a PHR, for example, after or in response toactivating the SCell.

The wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell activation/deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a timer (e.g., ansCellDeactivationTimer timer) associated with an activated SCellexpires. The wireless device may stop the timer (e.g.,sCellDeactivationTimer timer) associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may clear one or more configured downlink assignmentsand/or one or more configured uplink grant Type 2 associated with theactivated SCell, for example, after or in response to the deactivatingthe activated SCell. The wireless device may suspend one or moreconfigured uplink grant Type 1 associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may flush HARQ buffers associated with the activatedSCell.

A wireless device may not perform certain operations, for example, if anSCell is deactivated. The wireless device may not perform one or more ofthe following operations if an SCell is deactivated: transmitting SRS onthe SCell; reporting CQI, PMI, RI, and/or CRI for the SCell on a PCell;transmitting on UL-SCH on the SCell; transmitting on a RACH on theSCell; monitoring at least one first PDCCH on the SCell; monitoring atleast one second PDCCH for the SCell on the PCell; and/or transmitting aPUCCH on the SCell.

A wireless device may restart a timer (e.g., an sCellDeactivationTimertimer) associated with the activated SCell, for example, if at least onefirst PDCCH on an activated SCell indicates an uplink grant or adownlink assignment. A wireless device may restart a timer (e.g., ansCellDeactivationTimer timer) associated with the activated SCell, forexample, if at least one second PDCCH on a serving cell (e.g. a PCell oran SCell configured with PUCCH, such as a PUCCH SCell) scheduling theactivated SCell indicates an uplink grant and/or a downlink assignmentfor the activated SCell. A wireless device may abort the ongoing randomaccess procedure on the SCell, for example, if an SCell is deactivatedand/or if there is an ongoing random access procedure on the SCell.

FIG. 20A shows an example of an SCell activation/deactivation MAC CEthat may comprise one octet. A first MAC PDU subheader comprising afirst LCID may identify the SCell activation/deactivation MAC CE of oneoctet. An SCell activation/deactivation MAC CE of one octet may have afixed size. The SCell activation/deactivation MAC CE of one octet maycomprise a single octet. The single octet may comprise a first number ofC-fields (e.g., seven) and a second number of R-fields (e.g., one).

FIG. 20B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID may identifythe SCell Activation/Deactivation MAC CE of four octets. An SCellactivation/deactivation MAC CE of four octets may have a fixed size. TheSCell activation/deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g., 1). A C_(i) field mayindicate an activation/deactivation status of an SCell with an SCellindex i, for example, if an SCell with SCell index i is configured. AnSCell with an SCell index i may be activated, for example, if the C_(i)field is set to one. An SCell with an SCell index i may be deactivated,for example, if the C_(i) field is set to zero. The wireless device mayignore the C, field, for example, if there is no SCell configured withSCell index i. An R field may indicate a reserved bit. The R field maybe set to zero.

A base station may configure a wireless device with uplink (UL)bandwidth parts (BWPs) and downlink (DL) BWPs, for example, to enablebandwidth adaptation (BA) for a PCell. The base station may configurethe wireless device with at least DL BWP(s) (e.g., an SCell may not haveUL BWPS) to enable BA for an SCell, for example, if CA is configured.For the PCell, an initial BWP may be a first BWP used for initialaccess. For the SCell, a first active BWP may be a second BWP configuredfor the wireless device to first operate on the SCell if the SCell isactivated.

A base station and/or a wireless device may switch a DL BWP and an ULBWP independently, for example, in paired spectrum (e.g., FDD). A basestation and/or a wireless device may switch a DL BWP and an UL BWPsimultaneously, for example, in unpaired spectrum (e.g., TDD). Switchingbetween configured BWPs may be based on DCI and/or an inactivity timer.The base station and/or the wireless device may switch an active BWP toa default BWP, for example, based on or in response to an expiry of theinactivity timer associated with a cell (e.g., if the inactivity timeris configured for a serving cell). The default BWP may be configured bythe network.

One UL BWP for each uplink carrier and one DL BWP may be active at atime in an active serving cell, for example, in FDD systems configuredwith BA. One DL/UL BWP pair may be active at a time in an active servingcell, for example, in TDD systems. Operating on the one UL BWP and theone DL BWP (and/or the one DL/UL pair) may enable a wireless device touse a reasonable amount of power (e.g., reasonable battery consumption).BWPs other than the one UL BWP and the one DL BWP that the wirelessdevice may be configured with may be deactivated. The wireless devicemay refrain from monitoring a PDCCH, and/or may refrain fromtransmitting via a PUCCH, PRACH and/or UL-SCH, for example, ondeactivated BWPs.

A serving cell may be configured with a first number (e.g., four) ofBWPs. A wireless device and/or a base station may have one active BWP atany point in time, for example, for an activated serving cell. A BWPswitching for a serving cell may be used to activate an inactive BWPand/or deactivate an active BWP. The BWP switching may be controlled bya PDCCH indicating a downlink assignment or an uplink grant. The BWPswitching may be controlled by an inactivity timer (e.g.,bandwidthpartInactivityTimer). The BWP switching may be controlled by aMAC entity, for example, based on initiating a random access procedure.A BWP may be initially active without receiving a PDCCH indicating adownlink assignment or an uplink grant, for example, based on anaddition of an SpCell or an activation of an SCell. The active BWP for aserving cell may be indicated by an RRC message and/or a PDCCH message(e.g., PDCCH order). A DL BWP may be paired with an UL BWP, and/or BWPswitching may be common for both UL and DL, for example, for unpairedspectrum.

FIG. 21 shows an example of BWP switching. The BWP switching may be on aPCell. A base station 2102 may send (e.g., transmit) one or moremessages (e.g., one or more RRC messages) 2112 for configuring multipleBWPs (e.g., multiple BWPs comprising a DL BWP 0, a DL BWP 1, a DL BWP 2,a DL BWP 3, a UL BWP 0, a UL BWP 1, a UL BWP 2, and a UL BWP 3 shown ina table 2108). The DL (and/or UL) BWP 0 may be a default BWP. The DL(and/or UL) BWP 1 may be an initial active BWP (e.g., an initial DL BWPor an initial UL BWP). A wireless device 2104 may determine the multipleBWPs configured for the wireless device 2104, for example, based on theone or more messages 2112. The base station 2102 may send DCI 2114 for aDL assignment (e.g., at a time n). The DCI 2114 may be sent via the DLBWP 1 (e.g., an initial DL BWP). The wireless device 2104 may receive apacket via the DL BWP 1 or via another active DL BWP (e.g., at a timen+k), for example, based on the DL assignment. The wireless device 2104may start a BWP inactivity timer (e.g., at the time n+k). The wirelessdevice 2104 may start the BWP inactivity timer, for example, afterreceiving scheduled downlink packets. The base station 2102 may send DCI2114 for a UL grant (e.g., at the time n). The DCI 2114 may be sent viathe DL BWP 1 (e.g., a first DL BWP or an initial DL BWP). The wirelessdevice 2104 may send a packet via a UL BWP 1 (e.g., via a first UL BWPor an initial UL BWP at a time n+k), for example, based on the UL grant.The wireless device 2104 may start a BWP inactivity timer (e.g., at thetime n+k). The wireless device 2104 may start the BWP inactivity timer,for example, after sending scheduled uplink packets.

The base station 2102 may send DCI 2116 for BWP switching (e.g., a BWPswitching from the DL BWP 1 to the DL BWP 2). The DCI 2116 may be sentvia the active DL BWP 1 (e.g., at a time m). The wireless device 2104may receive the DCI 2116, for example, by monitoring a PDCCH on theactive DL BWP 1. The wireless device 2104 may switch the DL BWP 1 to theDL BWP 2 (e.g., at a time m+l), for example, based on the DCI 2116.There may be a delay (e.g., a gap) between the wireless device 2104receiving the DCI 2116 and the wireless device 2104 switching to the DLBWP 2. The wireless device 2104 may start and/or re-start the BWPinactivity timer (e.g., at the time m+l), for example, after the BWPswitching. The BWP inactivity timer may expire (e.g., at a time o), forexample, if the wireless device 2104 does not perform reception ortransmission for a period of time (e.g., a period from the time m+l tothe time o). The wireless device 2104 may switch the DL BWP 2 to the DLBWP 0 (e.g., a default BWP). The fallback to the DL BWP 0 may occur(e.g., at a time o+q), for example, after the BWP inactivity timerexpires. There may be a delay (e.g., a gap) between the BWP timerexpiration (e.g., at a time o) and the wireless device 2104 switching tothe DL BWP 0 (e.g., at a time o+q). BWPs are described as exampleresources, and any wireless resource may be applicable to one or moreprocedures described herein.

FIG. 22 shows an example of BWP switching. The BWP switching may beperformed on an SCell. A base station 2202 may send (e.g., transmit) oneor more messages (e.g., one or more RRC messages) 2212 for configuringmultiple BWPs (e.g., multiple BWPs comprising a DL BWP 0, a DL BWP 1, aDL BWP 2, a DL BWP 3, a UL BWP 0, a UL BWP 1, a UL BWP 2, and a UL BWP 3shown in tables 2206 and 2208, respectively). The multiple BWPs may beBWPs of an SCell. The DL (and/or UL) BWP 0 may be a default BWP. The DL(and/or UL) BWP 1 may be a first (or initial) active BWP (e.g., a firstDL BWP or a first UL BWP). A wireless device 2204 may determine themultiple BWPs configured for the wireless device 2204, for example,based on the one or more messages 2212. The base station 2202 may send,to the wireless device 2204, a MAC CE 2214 for activating the SCell(e.g., at a time n). The wireless device 2204 may activate the SCell(e.g., at a time n+k). The wireless device 2204 may start to monitor aPDCCH on (e.g., sent via) the DL BWP 1. The base station 2202 may sendDCI 2216 for a DL assignment (e.g., at a time m). The DCI 2216 may besent via the DL BWP 1 (e.g., a first DL BWP). The wireless device 2204may receive a packet via the DL BWP 1 or via another active DL BWP(e.g., at a time m+l), for example, based on the DL assignment. Thewireless device 2204 may start a BWP inactivity timer (e.g., at the timem+l). The wireless device 2204 may start the BWP inactivity timer, forexample, after receiving scheduled downlink packets. The base station2202 may send DCI 2216 for a UL grant (e.g., at the time m). The DCI2216 may be sent via the DL BWP 1 (e.g., a first DL BWP or an initial DLBWP). The wireless device 2204 may send a packet via a UL BWP 1 (e.g.,via a first UL BWP or an initial UL BWP at a time m+l), for example,based on the UL grant. The wireless device 2204 may start a BWPinactivity timer (e.g., at the time m+l). The wireless device 2204 maystart the BWP inactivity timer, for example, after sending scheduleduplink packets.

The BWP inactivity timer may expire (e.g., at a time s). The BWPinactivity may expire, for example, if the wireless device 2204 does notperform reception or transmission for a period of time (e.g., a periodfrom the time m+l to the time s). The wireless device 2204 may switchthe DL BWP 1 to the DL BWP 0 (e.g., a default BWP). The fallback to theDL BWP 0 may occur (e.g., at a time s+t), for example, after the BWPinactivity timer expires. The base station 2202 may send, to thewireless device 2204, a MAC CE 2218 for deactivating the SCell (e.g., ata time o). The wireless device 2204 may deactivate the SCell and/or stopthe BWP inactivity timer (e.g., at a time o+p). The wireless device 2204may deactivate the SCell and/or stop the BWP inactivity timer, forexample, after receiving and/or checking an indication of the MAC CE2218.

A MAC entity may use operations on an active BWP for an activatedserving cell configured with a BWP, such as one or more of: transmittingvia an UL-SCH; transmitting via a RACH; monitoring a PDCCH; transmittingvia a PUCCH; receiving via a DL-SCH; initializing and/or reinitializingsuspended configured uplink grants of configured grant Type 1 accordingto a stored configuration, if any and/or to start in a symbol based on aprocedure. On an inactive BWP for each activated serving cell configuredwith a BWP, a MAC entity: may refrain from transmitting via an UL-SCH,may refrain from transmitting via a RACH, may refrain from monitoring aPDCCH, may refrain from transmitting via a PUCCH, may refrain fromtransmitting an SRS, may refrain from receiving via a DL-SCH, may clearany configured downlink assignment and configured uplink grant ofconfigured grant Type 2, and/or may suspend any configured uplink grantof configured Type 1.

A random access procedure (e.g., based on an initiation of the randomaccess procedure) on an active DL BWP and the active UL BWP may beperformed, for example, if PRACH resources are configured for the activeUL BWP. The random access procedure may be performed, for example, by aMAC entity. A MAC entity may switch to an initial DL BWP and an initialUL BWP, for example, if PRACH resources are not configured for an activeUL BWP (e.g., based on initiation of a random access procedure). The MACentity may perform the random access procedure on the initial DL BWP andthe initial UL BWP, for example, based on the BWP switching.

A wireless device may perform BWP switching to a BWP indicated by aPDCCH, for example, if a MAC entity receives a PDCCH (e.g., a PDCCHorder) for a BWP switching of a serving cell, for example, if a randomaccess procedure associated with this serving cell is not ongoing.

A wireless device may determine whether to switch a BWP or ignore thePDCCH for the BWP switching, for example, if a MAC entity received aPDCCH for a BWP switching while a random access procedure is ongoing inthe MAC entity. The MAC entity may stop the ongoing Random Accessprocedure and initiate a second Random Access procedure on a newactivated BWP, for example, if the MAC entity decides to perform the BWPswitching. The MAC entity may continue with the ongoing Random Accessprocedure on the active BWP, for example if the MAC decides to ignorethe PDCCH for the BWP switching. A wireless device may perform the BWPswitching to a BWP indicated by the PDCCH, for example, if a MAC entityreceives a PDCCH for a BWP switching addressed to a C-RNTI for asuccessful completion of a Random Access procedure.

The MAC entity may start or restart the BWP-InactivityTimer associatedwith the active DL BWP for a variety of reasons. The MAC entity maystart or restart the BWP-InactivityTimer associated with the active DLBWP, for example, if one or more of the following occur: aBWP-InactivityTimer is configured for an activated serving sell, if aDefault-DL-BWP is configured and an active DL BWP is not a BWP indicatedby the Default-DL-BWP, if the Default-DL-BWP is not configured and theactive DL BWP is not the initial BWP; and/or if one or more of thefollowing occur: if a PDCCH addressed to C-RNTI or CS-RNTI indicatingdownlink assignment or uplink grant is received on the active BWP,and/or if there is not an ongoing random access procedure associatedwith the activated serving cell.

The MAC entity may start or restart the BWP-InactivityTimer associatedwith the active DL BWP, for example, if one or more of the followingoccur: if a BWP-InactivityTimer is configured for an activated servingcell, if a Default-DL-BWP is configured and an active DL BWP is not aBWP indicated by the Default-DL-BWP, and/or if the Default-DL-BWP is notconfigured and the active DL BWP is not the initial BWP; and/or if oneor more of the following occur: if a MAC-PDU is transmitted in aconfigured uplink grant or received in a configured downlink assignment,and/or if there is not an ongoing random access procedure associatedwith the activated serving cell.

The MAC entity may start or restart the BWP-InactivityTimer associatedwith the active DL BWP, for example, if one or more of the followingoccur: if a BWP-InactivityTimer is configured for an activated servingcell, if a Default-DL-BWP is configured and an active DL BWP is not aBWP indicated by the Default-DL-BWP, and/or if the Default-DL-BWP is notconfigured and the active DL BWP is not the initial BWP; and/or if oneor more of the following occur: if a PDCCH addressed to C-RNTI orCS-RNTI indicating downlink assignment or uplink grant is received onthe active BWP, if a MAC-PDU is transmitted in a configured uplink grantor received in a configured downlink assignment, and/or if an ongoingrandom access procedure associated with the activated Serving Cell issuccessfully completed in response to receiving the PDCCH addressed to aC-RNTI.

The MAC entity may start or restart the BWP-InactivityTimer associatedwith the active DL BWP based on switching the active BWP. For example,the MAC entity may start or restart the BWP-InactivityTimer associatedwith the active DL BWP if a PDCCH for BWP switching is received and thewireless device switches an active DL BWP to the DL BWP, and/or if oneor more of the following occur: if a default downlink BWP is configuredand the DL BWP is not the default downlink BWP, and/or if a defaultdownlink BWP is not configured and the DL BWP is not the initialdownlink BWP.

The MAC entity may stop the BWP-InactivityTimer associated with anactive DL BWP of the activated serving cell, for example, if one or moreof the following occur: if BWP-InactivityTimer is configured for anactivated serving cell, if the Default-DL-BWP is configured and theactive DL BWP is not the BWP indicated by the Default-DL-BWP, and/or ifthe Default-DL-BWP is not configured and the active DL BWP is not theinitial BWP; and/or if a random access procedure is initiated. The MACentity may stop a second BWP-InactivityTimer associated with a secondactive DL BWP of an SpCell, for example, if the activated Serving Cellis an SCell (other than a PSCell).

The MAC entity may perform BWP switching to a BWP indicated by theDefault-DL-BWP, for example, if one or more of the following occur: if aBWP-InactivityTimer is configured for an activated serving cell, if theDefault-DL-BWP is configured and the active DL BWP is not the BWPindicated by the Default-DL-BWP, if the Default-DL-BWP is not configuredand the active DL BWP is not the initial BWP, if BWP-InactivityTimerassociated with the active DL BWP expires, and/or if the Default-DL-BWPis configured.. The MAC entity may perform BWP switching to the initialDL BWP, for example, if the MAC entity may refrain from performing BWPswitching to a BWP indicated by the Default-DL-BWP.

A wireless device may be configured for operation in BWPs of a servingcell. The wireless device may be configured by higher layers for theserving cell for a set of (e.g., four) bandwidth parts (BWPs) forreceptions by the wireless device (e.g., DL BWP set) in a DL bandwidthby a parameter (e.g., DL-BWP). The wireless device may be configuredwith a set of (e.g., four) BWPs for transmissions by the wireless device(e.g., UL BWP set) in an UL bandwidth by a parameter (e.g., UL-BWP) forthe serving cell. An initial active DL BWP may be determined, forexample, by: a location and number of contiguous PRBs; a subcarrierspacing; and/or a cyclic prefix (e.g., for the control resource set fora TypeO-PDCCH common search space). A wireless device may be provided(e.g., by a higher layer) a parameter (e.g., initial-UL-BWP) for aninitial active UL BWP for a random access procedure, for example, foroperation on a primary cell. The wireless device may be provided (e.g.,by a higher layer) a parameter (e.g., Active-BWP-DL-Pcell) for firstactive DL BWP for receptions, for example, if a wireless device has adedicated BWP configuration. The wireless device may be provided (e.g.,by a higher layer) a parameter (e.g., Active-BWP-UL-Pcell) for a firstactive UL BWP for transmissions on a primary cell, for example, if awireless device has a dedicated BWP configuration.

The wireless device may be configured with a variety of parameters for aDL BWP and/or for an UL BWP in a set of DL BWPs and/or UL BWPs,respectively, for a serving cell. The wireless device may be configuredwith one or more of: a subcarrier spacing (e.g., provided by higherlayer parameter DL-BWP-mu or UL-BWP-mu), a cyclic prefix (e.g., providedby higher layer parameter DL-BWP-CP or UL-BWP-CP), a PRB offset withrespect to the PRB (e.g., determined by higher layer parametersoffset-pointA-low-scs and ref-scs) and a number of contiguous PRBs(e.g., provided by higher layer parameter DL-BWP-BW or UL-BWP-BW), anindex in the set of DL BWPs or UL BWPs (e.g., by respective higher layerparameters DL-BWP-index or UL-BWP-index), a DCI format 1_0 or DCI format1_1 detection to a PDSCH reception timing values (e.g., provided byhigher layer parameter DL-data-time-domain), a PDSCH reception to aHARQ-ACK transmission timing values (e.g., provided by higher layerparameter DL-data-DL-acknowledgement), and/or a DCI 0_0 or DCI 0_1detection to a PUSCH transmission timing values (e.g., provided byhigher layer parameter UL-data-time-domain).

A DL BWP from a set of configured DL BWPs (e.g., with an index providedby higher layer parameter DL-BWP-index) may be paired with an UL BWPfrom a set of configured UL BWPs (e.g., with an index provided by higherlayer parameter UL-BWP-index). A DL BWP from a set of configured DL BWPsmay be paired with an UL BWP from a set of configured UL BWPs, forexample, if the DL BWP index and the UL BWP index are equal (e.g., forunpaired spectrum operation). A wireless device may not be expected toreceive a configuration where the center frequency for a DL BWP isdifferent from the center frequency for an UL BWP, for example, if theDL-BWP-index of the DL BWP is equal to the UL-BWP-index of the UL BWP(e.g., for unpaired spectrum operation).

A wireless device may be configured with control resource sets (e.g.,coresets) for every type of common search space and/or for wirelessdevice-specific search space, for example, for a DL BWP in a set of DLBWPs on a primary cell. The wireless device may not be expected to beconfigured without a common search space on the PCell, or on the PSCell,in the active DL BWP. The wireless device may be configured with controlresource sets for PUCCH transmissions, for example, for an UL BWP in aset of UL BWPs. A wireless device may receive a PDCCH message and/or aPDSCH message in a DL BWP, for example, according to a configuredsubcarrier spacing and/or a CP length for the DL BWP. A wireless devicemay transmit via a PUCCH and/or via a PUSCH in an UL BWP, for example,according to a configured subcarrier spacing and CP length for the ULBWP.

The BWP indicator field value may indicate an active DL BWP, from theconfigured DL BWP set, for DL receptions, for example, if a BWPindicator field is configured in DCI format 1_1. The BWP indicator fieldvalue may indicate the active UL BWP, from the configured UL BWP set,for UL transmissions. A wireless device may be provided (e.g., for theprimary cell) with a higher layer parameter (e.g., Default-DL-BWP, orany other a default DL BWP among the configured DL BWPs), for example,if a BWP indicator field is configured in DCI format 0_1. The defaultBWP may be the initial active DL BWP, for example, if a wireless deviceis not provided a default DL BWP by higher layer parameterDefault-DL-BWP. A wireless device may be expected to detect a DCI format0_1 indicating active UL BWP change, or a DCI format 1_1 indicatingactive DL BWP change, for example, if a corresponding PDCCH is receivedwithin first 3 symbols of a slot.

A wireless device may be provided (e.g., for a primary cell) with ahigher layer parameter (e.g., Default-DL-BWP, or any other a default DLBWP among the configured DL BWPs). The default DL BWP may be the initialactive DL BWP, for example, if a wireless device is not provided adefault DL BWP by the higher layer parameter Default-DL-BWP. A wirelessdevice may be provided with a higher layer parameter (e.g.,BWP-InactivityTimer) for a timer value for the primary cell. Thewireless device may increment the timer, if running, every interval of 1millisecond for frequency range 1, every 0.5 milliseconds for frequencyrange 2, or any other interval, for example, if the wireless device maynot detect a DCI format 1_1 for paired spectrum operation or, forexample, if the wireless device may not detect a DCI format 1_1 or DCIformat 0_1 for unpaired spectrum operation during the interval.

Wireless device procedures on the secondary cell may be same as on theprimary cell. Wireless device procedures may use the timer value for thesecondary cell and the default DL BWP for the secondary cell, forexample, if a wireless device is configured for a secondary cell with ahigher layer parameter (e.g., Default-DL-BWP) indicating a default DLBWP among the configured DL BWPs and the wireless device is configuredwith a higher layer parameter (e.g., BWP-InactivityTimer) indicating atimer value. The wireless device may use the indicated DL BWP and theindicated UL BWP on the secondary cell as the respective first active DLBWP and first active UL BWP on the secondary cell or carrier, forexample, if a wireless device is configured by a higher layer parameter(e.g., Active-BWP-DL-SCell) for a first active DL BWP and by a higherlayer parameter (e.g., Active-BWP-UL-SCell) for a first active UL BWP ona secondary cell or carrier.

A wireless device may have difficulty in determining whether DCI isindicating a BWP switching, a BWP activation, or a BWP deactivation, forexample, if multiple active BWPs in a cell (e.g., PCell or SCell) aresupported. A DCI format may be used (e.g., any legacy DCI format, a DCIformat of NR Release 15, or any other DCI format). The DCI format maycomprise a BWP index indicating a new BWP. Misalignment between a basestation and the wireless device may occur regarding a state of a BWP. Abase station may send (e.g., transmit) DCI comprising: a first fieldindicating a BWP, and/or a second field indicating a BWP action. The BWPaction may comprise one or more of: switching to the BWP, activating theBWP, and/or deactivating the BWP. A base station may send (e.g.,transmit) a MAC CE comprising an n-bit bitmap (e.g., an 8-bit bitmapassociated with 4 bits for DL BWPs and/or 4 bits for UL BWPs, or anyother quantity of bits) indicating that one or more BWPs may beactivated/deactivated (e.g., activated or deactivated). A base stationmay designate a first BWP of a cell as a primary active BWP. The basestation may send (e.g., transmit), via the primary active BWP, DCIactivating/deactivating (e.g., activating or deactivating) a secondaryBWP of the cell.

Multiple active BWPs may increase spectral efficiency, communicationspeed, interference mitigation, provide service-friendly BWP management,and/or other performance measures, for example, relative to aconfiguration supporting a single active BWP at a time (e.g., a singleDL BWP and a single UL BWP at a time). Multiple active BWPs may supporta plurality of active DL BWPs and/or a plurality of active UL BWPs.Configuring multiple active BWPS may require more complex BWP controlprotocols and technical designs, for example, relative to a singleactive BWP configuration. Some RRC signaling and/or DCI formats (e.g.,legacy signaling and/or format, and/or other signaling and/or formats)may cause one or more problems, such as the misalignment between a basestation and a wireless device regarding states of multiple BWPs.

One or more RRC signaling messages and/or one or more DCI formats may beenhanced. An RRC message may configure multiple active BWPs. An RRCmessage may configure one or more primary BWPs and one or more secondaryBWPs. An RRC message may configure whether the one or more primary BWPsare switchable by DCI and/or a MAC CE. An RRC message may configuredifferent BWPs for sending DCI for indicating a BWP change, for example,based on whether the one or more primary BWPs are switchable by DCIand/or a MAC CE. DCI may have a plurality of fields associated with aBWP control. A first field of DCI may indicate a BWP ID. A second fieldof the DCI may indicate an action associated with a BWP indicated by theBWP ID. The second field may have different sizes, for example,depending on different configurations and/or requirements. The size ofthe second field may be (e.g., semi-statically) changed (e.g., based onone or more RRC messages). The size of the second field may bedetermined, for example, based on whether a designated BWP is indicatedas a primary active BWP and/or whether the designated BWP is allowed tobe switched dynamically.

One or more MAC CEs may be configured for a plurality of BWP control,for example, if multiple active BWPs are supported. A MAC CE maycomprise a bitmap associated with a plurality of DL BWPs and/or aplurality of UL BWPs. The MAC CE may indicate activation/deactivation ofeach of multiple BWPs.

Some communications (e.g., communications based on one or more DCIs) mayenable dynamic BWP state changes without (or with reduced) processingdelays and may avoid or reduce misalignments between a base station anda wireless device. These communications may be applicable, for example,if services, channel quality, and/or traffic loading on BWPs changefrequently. Some other communications (e.g., communications based on oneor more MAC CEs) may provide more robust BWP state controls and/or mayreduce blind decoding complexity and/or power consumption of wirelessdevices. The latter communications may change states of a plurality ofBWPs at the same time and may reduce signaling overhead. The lattercommunications may be applicable, for example, if services, channelquality, and/or traffic loading on BWPs change infrequently. Differentcommunications may be used together or may be separately configuredbetween a base station and a wireless device, for example, depending onvarying requirements and signaling environments.

A base station may send (e.g., transmit) to, or receive from, a wirelessdevice one or more data packets. The one or more data packets may besent, or received, via one or more radio resources. The one or more datepackets may be one or more URLLC (Ultra-Reliable Low LatencyCommunication) data packets with a small packet size (e.g., <100 bytes),which may require ultra-reliable (e.g., BLER less than 10{circumflexover ( )}⁽⁻⁵⁾) and low latency delivery (e.g., less than 1 millisecond)between the base station and the wireless device. The one or more datapackets may be one or more eMBB (enhanced Mobile Broadband) data packetswith a large packet size (e.g., >1000 bytes), which may require a largebandwidth (e.g., 400 MHz˜1 GHz) and/or a large amount of radio resourcesfor transmission. The one or more date packets may be one or moremachine-type communication (e.g., MTC) data packets with a small packetsize, which require a wide communication coverage (e.g., 10 KM˜100 KM)or a transmission to a wireless device located in a basement. Othertypes of the one or more data packets may comprise vehicle to everything(V2X) packet(s) which may be transmitted between vehicles, or betweenvehicle and pedestrian, or between vehicle and roadside node, packet ofindustrial internet of things (HOT), and the like. It may be beneficialto transmit a first type of service (eMBB, URLLC, MTC, V2X and/or HOT)on a first active BWP of a cell and transmit a second type of service(eMBB, URLLC, V2X and/or HOT) on a second active BWP of the cell, forexample, if multiple services are launched in a cell. BWP and/or CAoperation configurations may support at most one active BWP in a cell.The BWP and/or CA operation configurations may be less efficient and/orresult in significant transmission latency, for example, if a basestation attempts to send (e.g., transmit), to a wireless device, datapackets for multiple services on multiple active BWPs.Activation/deactivation of an SCell based on a MAC CE (e.g., for addingan additional active BWP) may take a long time (e.g., several tens ofmilliseconds) and a significant delay may occur, for example, if thebase station attempts to send the data packets by frequently activatingand/or deactivating the multiple BWPs. Data transmission associated withsome types of service on an additional active BWP of the SCell may notbe tolerant of a delay caused by the activation/deactivation. Thetransmission latency may be improved, for example, by supportingmultiple active BWPs in a cell.

A base station and/or a wireless device may be configured with multipleBWPs for a cell. A base station and a wireless device may communicatewith each other via multiple active BWPs of the multiple BWPs inparallel (e.g., simultaneously or overlapped in time) to accommodatemultiple services (e.g., eMBB, URLLC, VTX, HOT, and/or MTC). A basestation may send (e.g., transmit), via a first active BWP, an eMBB datapacket to a wireless device. The base station may send (e.g., transmit),via a second active BWP, a URLLC data packet to the wireless device. Thebase station may send (e.g., transmit), via a third active BWP, an MTCdata packet to the wireless device. Transmitting multiple data packetsfor different services via different active BWPs in parallel (e.g.,simultaneously or overlapped in time) may reduce latency. Transmittingfirst data (e.g., eMBB data) and second data (e.g., URLLC data) via asingle active BWP may cause interruption of one transmission (e.g., theeMBB data transmission) by another transmission (e.g., the URLLC datatransmission). Transmitting multiple data packets for different servicesvia different active BWPs in parallel (e.g., simultaneously oroverlapped in time) may avoid the interruption. Physical and MAC layerprocedures configured for the BWP operation configuration that does notsupport multiple active BWPs in a cell may not be suitable for the BWPoperation configuration that supports multiple active BWPs in a cell(e.g., such an implementation may result in an inefficient BWPmanagement process). Multiple active BWPs may not be efficientlysupported in some systems (e.g., legacy systems and/or NR physical layerand MAC layer operation procedures). Physical layer and MAC layerprocedures may be enhanced, and evolved signaling for an efficient BWPoperation procedure may be configured to support multiple active BWPsoperation in a cell.

A base station may send (e.g., transmit), to a wireless device, one ormore messages comprising configuration parameters of a cell. The one ormore messages may comprise one or more RRC messages (e.g., an RRCconnection reconfiguration message, an RRC connection reestablishmentmessage, and/or an RRC connection setup message). The cell may be aPCell (or a PSCell) or an SCell, for example, if a carrier aggregationor dual connectivity is configured. The cell may comprise a plurality ofdownlink BWPs. Each of the plurality of downlink BWPs may be associatedwith a BWP ID (e.g., a BWP specific ID) and/or one or more parameters.The cell may comprise a plurality of uplink BWPs. Each of the pluralityof uplink BWPs may be associated with a BWP ID (e.g., a BWP specific ID)and/or one or more second parameters.

Each of the plurality of the downlink BWPs may be in one of an activestate and an inactive state. A wireless device may perform operationsvia an active BWP (e.g., a DL BWP or a UL BWP). The operations maycomprise transmitting a UL-SCH, transmitting a RACH, monitoring a PDCCH,transmitting a PUCCH, receiving a DL-SCH, and/or initializing (orreinitializing) any suspended configured uplink grants of configuredgrant Type 1 according to a stored configuration. For an inactive BWP(e.g., a DL BWP or a UL BWP), the wireless device may not transmit aUL-SCH, may not transmit a RACH, may not monitor a PDCCH, may nottransmit a PUCCH, may not transmit an SRS, may not receive a DL-SCH, mayclear any configured downlink assignment and configured uplink grant ofconfigured grant Type 2, and/or may suspend any configured uplink grantof configured Type 1.

The one or more parameters (and/or the one or more second parameters)may comprise at least one of: a control resource set identified by acontrol resource set index; a subcarrier spacing; a cyclic prefix; aDM-RS scrambling sequence initialization value; a number of consecutivesymbols; a set of resource blocks in frequency domain; a CCE-to-REGmapping; an REG bundle size; a cyclic shift for the REG bundle; anantenna port quasi-co-location; and/or an indication for a presence orabsence of a TCI field for DCI format 1_0 or 1_1 transmitted on thecontrol resource set. The one or more parameters may comprisecell-specific parameters. The one or more second parameters may compriseBWP-specific parameters. The configuration parameters may furtherindicate at least one of: an initial active DL BWP, of the plurality ofDL BWPs, identified by a first BWP ID and/or a default DL BWP, of theplurality of DL BWPs, identified by a second BWP ID. The second BWP IDmay be same as, or different from, the first BWP ID. The default DL BWPmay be in inactive state, for example, if the second BWP ID is differentfrom the first BWP ID of the initial active DL BWP.

The initial active DL BWP may be associated with one or more controlresource set for one or more common search space (e.g., typeO-PDCCHcommon search space). A wireless device may monitor a first PDCCH sentvia the initial active DL BWP of a PCell (or a PSCell) to detect DCI inthe first PDCCH, for example, if the wireless device switches from RRCidle state to RRC connected state.

A base station may activate an additional BWP dynamically (e.g., viaDCI, a MAC CE, etc.), for example, if at least one of multiple types ofservices are triggered for transmission via the additional BWP. The basestation may send (e.g., transmit) a first command to the wireless deviceto activate a second DL BWP, of the plurality of DL BWPs, indicated(e.g., identified) by a third BWP ID. The first command may be a MAC CEor DCI. The third BWP ID may be different from the first BWP ID and/ordifferent from the second BWP ID. The wireless device may transition(e.g., switch) the second DL BWP from inactive state to active stateand/or may maintain the initial active BWP in active state, for example,after or in response to the activating. The wireless device may monitora first PDCCH sent via the initial active DL BWP. The wireless devicemay monitor a second PDCCH sent via the second DL BWP in parallel (e.g.,simultaneously or overlapped in time), for example, after or in responseto the activating. Activating the second DL BWP may not change the stateof the initial active DL BWP.

FIG. 23A shows an example of configuring multiple active BWPs. The basestation may send (e.g., transmit) the first command (e.g., at a time T1)to the wireless device to activate another BWP (e.g., an A-BWP2), forexample, if there is at least one active DL BWP (e.g., an A-BWP1) of aplurality of active BWPs in a cell. The A-BWP2 may be different from theA-BWP1. The wireless device may transition (e.g., switch) the A-BWP2from inactive state to active state and/or maintain the A-BWP1 in activestate (e.g., at a time T2 after the time T1). Activating the A-BWP2 maynot change the state of the A-BWP1.

A base station may send (e.g., transmit), to a wireless device, one ormore RRC messages comprising configuration parameters indicating a firstactive DL BWP and at least one second active DL BWP of a PCell (or aPSCell), for example, if multiple active BWPs are supported by thewireless device. The wireless device may monitor a first PDCCH sent viathe first active DL BWP of a PCell (or a PSCell) and monitor at leastone second PDCCH sent via the at least one second active DL BWP of thePCell (or the PSCell). The wireless device may monitor the first PDCCHand the at least one second PDCCH to detect one or more DCIs (e.g., whenthe wireless device is in RRC connected mode or the wireless devicesswitches from RRC idle state to RRC connected state). Configuringmultiple active BWPs by the one or more RRC messages may reducesignaling overhead for BWP activation.

A base station may send (e.g., transmit), to a wireless device, one ormore RRC messages comprising configuration parameters indicating a firstactive DL BWP of an SCell and at least one second active DL BWP of theSCell, for example, if multiple active BWPs are supported by thewireless device. The wireless device may monitor a first PDCCH sent viathe first active DL BWP and at least one second PDCCH sent via the atleast one second active DL BWP of the SCell. The wireless device maymonitor the first PDCCH and the at least one second PDCCH to detect oneor more DCIs (e.g., after or in response to the SCell being activated bya MAC CE or DCI). Configuring multiple active BWPs by the one or moreRRC messages may reduce signaling overhead for BWP activation.

FIG. 23B shows an example of a BWP switching if multiple active BWPs aresupported. A base station may send (e.g., transmit) a second command toa wireless device to switch from an A-BWP1 to an A-BWP3 (at a time T2),for example, if there are at least two active DL BWPs (e.g., the A-BWP1and an A-BWP2) of a plurality of active BWPs in a cell (at a time T1before the time T2). The A-BWP1 may be the initial active DL BWPconfigured by the one or more messages. The A-BWP2 may be a DL BWPactivated by the first command The second command may be a MAC CE orDCI. The A-BWP3 may be different from the A-BWP1 and from the A-BWP2.The wireless device may transition (e.g., switch) the A-BWP1 from activestate to inactive state, transition (e.g., switch) the A-BWP3 frominactive state to active state, and/or maintain the A-BWP2 in activestate, for example, after or in response to the switching. The wirelessdevice may monitor a first PDCCH sent via the A-BWP3 and/or monitor asecond PDCCH sent via the A-BWP2 in parallel (e.g., simultaneously oroverlapped in time), for example, after or in response to the switching.Switching to the A-BWP3 from A-BWP1 may comprise deactivating the A-BWP1and activating the A-BWP3.

FIG. 23C shows an example of BWP deactivation if multiple active BWPsare supported. A base station may send (e.g., transmit) a third commandto a wireless device to deactivate an A-BWP2, for example, if there areat least two active DL BWPs (e.g., an A-BWP1 and the A-BWP2) of aplurality of active BWPs in a cell. The third command may be a MAC CE orDCI. The base station and/or the wireless device may deactivate theA-BWP2, for example, after or in response to an expiration of a BWPinactivity timer (e.g., associated with the A-BWP2 or associated withthe cell). The deactivating may comprise transiting (e.g., switching)the A-BWP2 from active state to inactive state and/or maintaining theA-BWP1 in active state (e.g., at a time T2). The wireless device maymonitor a first PDCCH sent via the A-BWP1 and/or stop monitoring asecond PDCCH associated with the A-BWP2, for example, after or inresponse to the deactivating. The deactivating the A-BWP2 may not changethe state of the A-BWP1 (e.g., the active state of the A-BWP1).

A base station and/or a wireless device may communicate via more thantwo active DL BWPs in a cell. The base station and/or the wirelessdevice may perform BWP activation, BWP deactivation, and BWP switching,for example, to flexibly provide different services. A base stationand/or a wireless device may maintain a first active DL BWP for a firsttransmission of a first service. The base station may activate a secondDL BWP to be a second active DL BWP, for example, if a second service istriggered. The wireless device may monitor one or more PDCCHs and/orreceive data packets on both the first active DL BWP and the secondactive DL BWP, for example, after or in response to the activating. Thebase station and/or the wireless device may activate a third DL BWP tobe a third active DL BWP, for example, if a third service is triggered.The wireless device may monitor one or more PDCCHs and/or receive datapackets on the first active DL BWP, the second active DL BWP, and thethird active DL BWP, for example, after or in response to theactivating.

A base station may cross-BWP schedule a second active DL BWP based on afirst active DL BWP, for example, which may reduce blind decodingcomplexity. Cross-BWP scheduling may comprise scheduling, by a basestation, a transmission (e.g., downlink or uplink transmissions) on ashared channel (e.g., downlink or uplink shared channels) of a secondBWP via control channels of a first BWP. The first active DL BWP may beconfigured with a first number of control resource sets and/or a secondnumber of search spaces. The second active DL BWP may be configured witha third number of control resource sets, and/or a fourth number ofsearch spaces. The first number may be greater than the third number.The second number may be greater than the fourth number. The secondactive DL BWP may be configured with no PDCCH resource.

FIG. 24A shows an example of a cross-BWP scheduling. A base station maysend (e.g., transmit), to a wireless device, a first PDCCH 2401A via afirst active DL BWP (e.g., a BWP 1) to schedule a first PDSCH 2411A ofthe BWP 1. The base station may send (e.g., transmit) a second PDCCH2402A via the BWP 1 to schedule a second PDSCH 2412A of a second activeBWP (e.g., a BWP 2), for example, if the BWP 2 is configured to becross-BWP scheduled by the BWP 1. The base station may send (e.g.,transmit) a third PDCCH 2403A via the BWP 1 to schedule a third PDSCH2413A of a third active BWP (e.g., a BWP 3), for example, if the BWP 3is configured to be cross-BWP scheduled by the BWP 1. The base stationmay send (e.g., transmit) a fourth PDCCH 2404A via the BWP 3 to schedulea fourth PDSCH 2414A of the BWP 3, for example, if BWP 3 is configuredto be self-scheduled. A wireless device may monitor one or more PDCCHssent via the BWP 1 for at least one second BWP, for example, if thecross-BWP scheduling is supported and the at least one second BWP isconfigured to be cross-BWP scheduled by the BWP 1. The first PDCCH2401A, the second PDCCH 2402A, and the third PDCCH 2403A may be threedistinct PDCCHs on a same search space. Each of the three distinctPDCCHs may be sent via different locations in the same search space.

FIG. 24B shows an example of a self-BWP scheduling. A PDSCH of an activeBWP may be self-scheduled by a PDCCH of the active BWP. A base stationmay schedule a first PDSCH resource 2411B on a first active BWP (e.g., aBWP 1) by a first PDCCH 2401B on the first active BWP. The base stationmay schedule a second PDSCH resource 2412B on a second active BWP (e.g.,a BWP 2) by a second PDCCH 2402B on the second active BWP. The basestation may schedule a third PDSCH resource 2413B on a third active BWP(e.g., a BWP 3) by a third PDCCH 2403B on the third active BWP.

A wireless device may monitor one or more PDCCHs in one or more commonsearch spaces on the multiple active DL BWPs, for example, with multipleactive DL BWPs in a cell (e.g., as shown in FIG. 23A, FIG. 23B and FIG.23C). Each of the multiple active DL BWPs may be associated with one ofthe one or more common search spaces. Configuring a common search spacefor each of multiple active DL BWPs may not be efficient for a PDCCHresource utilization in the cell. Configuring a common search space foreach of the multiple active DL BWPs may require a wireless device tomonitor multiple common search spaces for the multiple active DL BWPs,which may consume battery power in an inefficient manner PDCCH resourceutilization efficiency and battery power efficiency may be improved byone or more configurations described herein. The one or moreconfigurations may comprise designating a first active DL BWP, ofmultiple active DL BWPs, as a primary active DL BWP (PBWP). The primaryactive DL BWP may be the initial active DL BWP configured in the one ormore messages. The primary active DL BWP may be associated with one ormore common search spaces, and/or one or more wireless device-specificsearch spaces (e.g., UE-specific search spaces). The primary active BWPmay be a BWP via which the wireless device may perform an initialconnection establishment procedure or may initiate a connectionre-establishment procedure. The primary active DL BWP may be associatedwith one or more common search spaces for one or more DCI formats withCRC scrambled by one of SI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, INT-RNTI,SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CS-RNTI,SP-CSI-RNTI, and/or C-RNTI. The one or more common search spaces maycomprise at least one of: a type0-PDCCH common search space; atype0A-PDCCH common search space; a typel-PDCCH common search space; atype2-PDCCH common search space; and/or a type3-PDCCH common searchspace. The one or more DCI formats may comprise at least one of: a DCIformat 0_0; a DCI format 0_1; a DCI format 1_0; a DCI format 1_1; a DCIformat 2_0; a DCI format 2_1; a DCI format 2_2; and/or a DCI format 2_3.

The determination of the PBWP may be indicated by an RRC message, afirst MAC CE, and/or first DCI. At least one second active DL BWP of themultiple active DL BWPs may be designated as at least one secondaryactive DL BWP (SBWP). The determination of the at least one SBWP may beindicated by a second MAC CE and/or second DCI. A secondary active DLBWP may be associated with one or more wireless device-specific searchspaces. A wireless device may monitor one or more common search spacesand one or more first wireless device-specific search spaces on a PBWPof the cell and/or one or more second wireless device-specific searchspaces on an SBWP of the cell, for example, if the PBWP and the SBWP aredesignated in the cell.

FIG. 25A shows an example of a PBWP switching. A base station maydesignate, from the multiple active DL BWPs, a first active DL BWP as aPBWP (e.g., a PBWP1), and a second active DL BWP as an SBWP (e.g., anSBWP1), for example, if multiple DL BWPs are in active states in a cell.A wireless device may monitor a first PDCCH on the PBWP1 and a secondPDCCH on the SBWP1 (e.g., at a time T1). A base station may send (e.g.,transmit), to a wireless device, a first command to instruct a switchfrom the PBWP1 to a third BWP as a new primary BWP (e.g., a PBWP2). Thewireless device may transition (e.g., switch) the PBWP1 from activestate to inactive state and transition (e.g., switch) the third BWP(e.g., the PBWP2) from inactive state to active state, for example,after or in response to switching from the PBWP1 to the PBWP2. Theactivated third BWP may be a primary active BWP, for example, after orin response to the switching. The wireless device may monitor a firstPDCCH on common search spaces and first wireless device-specific searchspaces on the PBWP2 and/or may monitor a second PDCCH on second wirelessdevice-specific search spaces on the SBWP1, for example, after or inresponse to the switching from the PBWP1 to the PBWP2.

FIG. 25B shows an example of SBWP activation. A base station may send(e.g., transmit) a second command to a wireless device to activate asecond DL BWP (e.g., an SBWP1) as a secondary BWP, for example, if aprimary active BWP (e.g., a PBWP1) of a plurality of active BWPs aredesignated in a cell. The second DL BWP may be different from the PBWP1and/or the plurality of active BWPs. The wireless device may transition(e.g., switch) the second DL BWP from inactive state to active state andmaintain the PBWP1 in active state, for example, after or in response tothe activating. The second DL BWP may be designated as an SBWP (e.g., anSBWP1), for example, after or in response to the activation. Thewireless device may monitor a first PDCCH on common search spaces andfirst wireless device-specific search spaces on the PBWP1 and maymonitor a second PDCCH on second wireless device-specific search spaceson the SBWP1, for example, after or in response to the activation.

FIG. 25C shows an example of SBWP switching. A base station may assign,to a wireless device and/or from the multiple active DL BWPs, a firstactive DL BWP as a PBWP (e.g., a PBWP1) and a second active DL BWP as anSBWP (e.g., an SBWP1), for example, if a primary active BWP (e.g., thePBWP1) of a plurality of active BWPs is designated in a cell. Thewireless device may monitor a first PDCCH on a PBWP1 and/or a secondPDCCH on an SBWP1. The base station may send (e.g., transmit), to thewireless device, a third command to switch from the SBWP1 to a third BWP(e.g., an SBWP2) as a new secondary BWP. The wireless device maytransition (e.g., switch) the SBWP1 from active state to inactive stateand/or transition (e.g., switch) the third BWP from inactive state toactive state, for example, after or in response to switching from theSBWP1 to the SBWP2. The activated third BWP may be a secondary activeBWP, for example, after or in response to the switching. The wirelessdevice may monitor the first PDCCH on common search spaces and/or firstwireless device-specific search spaces on the PBWP1 and/or a third PDCCHon second wireless device-specific search spaces on the SBWP2, forexample, after or in response to the switching from the SBWP1 to theSBWP2.

FIG. 25D shows an example of SBWP deactivation from a configuration inwhich multiple active DL BWPs are supported. A base station may send(e.g., transmit) a fourth command to a wireless device to deactivate anSBWP1, for example, if a primary active BWP (e.g., a PBWP1) and asecondary active BWP (e.g., the SBWP1) of a plurality of active DL BWPsare designated in a cell. The fourth command may be a MAC CE or DCI. Thebase station and/or the wireless device may deactivate the SBWP1, forexample, after or in response to an expiration of a BWP inactivitytimer. The BWP inactivity timer may be associated with the SBWP1. Thewireless device may transition (e.g., switch) the SBWP1 from activestate to inactive state and/or maintain the PBWP1 in active state, forexample, after or in response to the deactivating. The wireless devicemay monitor a first PDCCH on (e.g., sent via) the PBWP1 and/or stopmonitoring a second PDCCH on (e.g., associated with) the SBWP1, forexample, after or in response to the deactivating. Deactivating theSBWP1 may not change the state of the PBWP1.

A base station and/or a wireless device may not allow a PBWP switchingto a second active BWP by a MAC CE or by DCI, for example, in aconfiguration in which multiple active DL BWPs comprise a PBWP and atleast one SBWP in a cell. The base station and/or the wireless devicemay trigger an SBWP deactivation, an SBWP activation, and/or an SBWPswitching. Configuring the PBWP to be unswitchable may simplifysignaling designs and/or reduce implementation complexity of thewireless device. The PBWP may be switched to the second PBWP, forexample, only by an RRC message but not by a MAC CE or DCI. The RRCmessage triggering a PBWP switching may enable a base station tostatically (or semi-statically) switch the PBWP. FIG. 26A, FIG. 26B andFIG. 26C show examples of configurations in which a PBWP is configuredto be unswitchable (e.g., always active), such as by DCI. Configuring aPBWP to be unswitchable (e.g., at least by DCI) may simplifyimplementation of procedures for a base station and a wireless device,reduce signaling overhead, and/or reduce battery consumption of thewireless device. A wireless device may switch the PBWP to a new PBWP,for example, after or in response to receiving an RRC message indicatingPBWP switching.

FIG. 26A shows an example of SBWP activation. A base station may send(e.g., transmit) a first command to a wireless device to activate asecond DL BWP as a secondary BWP (e.g., an SBWP1), for example, if aprimary active BWP (e.g., a PBWP1) of a plurality of active DL BWPs isdesignated in a cell. The second DL BWP may be different from the PBWP1and/or the plurality of active BWPs. The wireless device may transition(e.g., switch) the second DL BWP from inactive state to active state andmay maintain the PBWP1 in active state, for example, after or inresponse to the activating. The second DL BWP may be designated as anSBWP (e.g., an SBWP1), for example, after or in response to theactivation. The wireless device may monitor a first PDCCH on commonsearch spaces and/or first wireless device-specific search spaces onPBWP1 and/or a second PDCCH on second wireless device-specific searchspaces on the SBWP1, for example, after or in response to theactivation.

FIG. 26B shows an example of SBWP deactivation. A base station may send(e.g., transmit) a second command to a wireless device to deactivate theSBWP1, for example, if a primary active BWP (e.g., a PBWP1) and asecondary active BWP (e.g., the SBWP1) of a plurality of active DL BWPsare designated in a cell. The second command may be a MAC CE or DCI. Thebase station and/or the wireless device may deactivate the SBWP1, forexample, after or in response to an expiration of a BWP inactivitytimer. The BWP inactivity timer may be associated with the SBWP1. Thewireless device may transition (e.g., switch) the SBWP1 from activestate to inactive state and/or may maintain the PBWP1 in active state,for example, after or in response to the deactivating. The wirelessdevice may monitor a first PDCCH on (e.g., sent via) the PBWP1 and/ormay stop monitoring a second PDCCH on (e.g., associated with) the SBWP1,for example, after or in response to the deactivating.

FIG. 26C shows an example of SBWP switching. A base station may assign,to a wireless device and/or from multiple DL active BWPs, a first activeDL BWP as a PBWP (e.g., a PBWP1) and a second active DL BWP as an SBWP(e.g., an SBWP1), for example, if the multiple DL active BWPs areconfigured in a cell. The wireless device may monitor a first PDCCH on(e.g., sent via) the PBWP1 and a second PDCCH on (e.g., sent via) theSBWP1. A base station may send (e.g., transmit), to the wireless device,a third command to switch from the SBWP1 to a third BWP as a secondaryBWP (e.g., the SBWP2). The wireless device may transition (e.g., switch)the SBWP1 from active state to inactive state and/or transition (e.g.,switch) the third BWP from inactive state to active state, for example,after or in response to switching from the SBWP1 to the SBWP2. Theactivated third BWP may be the secondary active BWP (e.g., the SBWP2).The wireless device may monitor the first PDCCH on common search spacesand/or first wireless device-specific search spaces on the PBWP1 and/ora third PDCCH on second wireless device-specific search spaces on theSBWP2, for example, after or in response to the switching from the SBWP1to the SBWP2.

Some wireless devices (e.g., a first wireless device) may support atmost one active BWP in a cell. Other wireless devices (e.g., a secondwireless device) may support more than one active BWP in a cell. A basestation and/or the first wireless device may trigger a BWP switching toa second BWP as an active BWP.

Some wireless device (e.g., a second wireless device) may support aplurality of active BWPs in a cell. For at least some of these wirelessdevices (e.g., a second wireless device), no specific designation of aPBWP or an SBWP of the plurality of active BWPs may be performed (e.g.,as shown in FIGS. 23A, 23B, and 23C). Each of the plurality of activeBWPs may be associated with one or more common search spaces. The secondwireless device may communicate with the base station via the pluralityof active BWPs in the cell. The base station and/or the second wirelessdevice may trigger activating/deactivating a BWP and/or switching from afirst BWP to a second BWP as a second active BWP.

Some wireless devices (e.g., a third wireless device) may support aplurality of active BWPs in a cell. For some wireless devices (e.g., thethird wireless device), a PBWP and at least one SBWP of the plurality ofactive BWPs may be designated, and/or the PBWP may be maintained inactive state, for example, at least until the third wireless devicereceives an indication of (e.g., an RRC message indicating) a PBWPswitching. The PBWP may not be switched to a new active BWP dynamically(e.g., by DCI transmitted on a PDCCH). The third wireless device maycommunicate with the base station via the plurality of active BWPs inthe cell. The base station and/or the third wireless device may triggeractivating/deactivating an SBWP and/or switching from a first SBWP to asecond BWP as a second SBWP.

Some wireless devices (e.g., a fourth wireless device) may support aplurality of active BWPs in a cell. For the some wireless devices (e.g.,the fourth wireless device), a PBWP and at least one SBWP of theplurality of active BWPs may be designated, and/or the PBWP may beswitched to a new BWP as a new PBWP dynamically (e.g., by DCItransmitted on a PDCCH). The fourth wireless device may communicate withthe base station via the plurality of active BWPs in the cell. The basestation and/or the wireless device may trigger activating/deactivatingan SBWP, switching from a first PBWP to a second BWP as a second PBWP,and/or switching from a first SBWP to a third BWP as a second SBWP.

Different wireless devices may support different BWP operation modes. Awireless device may send (e.g., transmit) various information to a basestation indicating the wireless device's capability of one or more ofmultiple BWP operation modes in a cell. The multiple BWP operation modesin a cell may comprise at least one of: a first mode in which thewireless may support a single active BWP in the cell; a second mode inwhich the wireless device may support multiple active BWPs, without aPBWP designation, in the cell; a third mode in which the wireless devicemay support multiple active BWPs with a PBWP and at least one SBWPdesignated and the PBWP switchable by an RRC message; a fourth mode inwhich the wireless device may support multiple active BWPs with a PBWPand at least one SBWP designated and the PBWP switchable by DCI; a fifthmode in which the wireless device may support multiple active BWPs withmultiple PBWPs and multiple SBWPs designated and the PBWP switchable byan RRC or DCI; and/or any other modes. A base station may send (e.g.,transmit), to a wireless device, one or more messages indicating one ormore of the multiple BWP operation modes.

A base station and/or a wireless device may communicate via the multipleactive BWPs with a default BWP operation mode, for example, if multipleactive BWPs are supported. The default BWP operation mode may be one ofthe multiple BWP operation modes. A wireless device capable ofsupporting a first specification (e.g., a legacy device, a deviceconfigured to 3GPP Release 15, or a device configured for any otherspecification) may perform a BWP operation with the first mode (e.g.,supporting a single active BWP in a cell) of the multiple BWP operationmodes. A wireless device capable of supporting a second specification(e.g., a legacy device, a device configured to 3GPP Release 16, or adevice configured for any other specification) may perform a BWPoperation with the default BWP mode of the multiple BWP operation modes.To support multiple active BWPs in a cell, a default BWP mode may bepreconfigured (e.g., predefined) as one of the second mode, the thirdmode, the fourth mode, the fifth mode, and/or any other mode, ofmultiple BWP operation modes.

A base station may send (e.g., transmit), to a wireless device, one ormore messages comprising configuration parameters of a plurality of DLBWPs in a cell. Multiple DL BWPs of a plurality of DL BWPs may beactivated as active DL BWPs. A wireless device and/or a base station maycommunicate via the active DL BWPs comprising a PBWP and an SBWP. ThePBWP may switch to a first DL BWP as a new PBWP. The SBWP may switch toa second DL BWP as a new SBWP. The SBWP may be deactivated. A third BWPmay be activated as a second SBWP. A base station may send (e.g.,transmit) one or more DCIs indicating a PBWP switching, an SBWPactivation, an SBWP deactivation, an SBWP switching, and/or a PDSCHscheduling on a PBWP or on an SBWP. The indication by the one or moreDCIs may be, for example, based on at least one of: one or more valuesof one or more fields of the one or more DCI; and/or whether the one ormore DCI is transmitted via a PBWP or an SBWP. The one or more DCIs maybe sent (e.g., transmitted) with DCI format 1_0 or 1_1 indicating aPDSCH scheduling. The one or more fields may comprise at least one of: acarrier indicator; an identifier for a DCI format; a BWP indicator; afirst field indicating a frequency domain resource assignment; a secondfield indicating a time domain resource assignment; a PUCCH resourceindicator; a TPC command for a scheduled PUCCH; and/or aPDSCH-to-HARQ_feedback timing indicator. Reusing an existing DCI format(e.g., DCI format 1_0 or 1_1) for a BWP operation supporting multipleactive BWPs may reduce blind decoding complexity at a wireless device.

A wireless device may switch the PBWP to a first BWP as a new PBWPindicated (e.g., identified) by the BWP indicator, for example, based onat least one of: the one or more DCI being transmitted via the PBWP; theBWP indicator indicating the first BWP different from the PBWP and theSBWP (e.g., if configured); and/or a value of the first field and/or thesecond field being different from a first value (e.g., all zeros) and/ora second value (e.g., all ones). The first value and/or the second valuemay be predefined (e.g., fixed). The wireless device may switch the SBWPto a second BWP as a new SBWP indicated (e.g., identified) by the BWPindicator, for example, based on at least one of: the one or more DCIsbeing transmitted via the SBWP; the BWP indicator indicating the secondBWP different from the PBWP and from the SBWP; and/or a value of thefirst field and/or the second field being different from the first value(e.g., all zeros) and/or the second value (e.g., all ones).

The wireless device may activate a third BWP as a new SBWP indicated(e.g., identified) by the BWP indicator, for example, based on at leastone of: the BWP indicator indicating the third BWP different from thePBWP and from the SBWP; and/or the value of the first field and/or thesecond field being the first value (e.g., all zeros). The wirelessdevice may deactivate the SBWP, for example, based on at least one of:the one or more DCIs being transmitted via the PBWP; the BWP indicatorindicating the SBWP; and/or the value of the first field or the secondfield being the second value (e.g., all ones).

The wireless device may receive a DL assignment via a PBWP (e.g.,without a PBWP switching), for example, based on at least one of: theBWP indicator indicating the PBWP; and/or the value of the first fieldor the second field being different from the first value (e.g., allzeros) and/or the second value (e.g., all ones). The wireless device mayreceive a DL assignment via an SBWP (e.g., without an SBWPswitching/activation/deactivation), for example, based on at least oneof: the BWP indicator indicating the SBWP; and/or the value of the firstfield or the second field being different from the first value (e.g.,all zeros) and/or the second value (e.g., all ones). The wireless devicemay receive one or more DL data packets from a first PDSCH on (e.g.,sent via) the PBWP, for example, after or in response to receiving theDL assignment on the PBWP. The wireless device may receive one or moreDL data packets from a second PDSCH on (e.g., sent via) the SBWP, forexample, after or in response to receiving the DL assignment via theSBWP.

The base station and the wireless device may dynamically switch a PBWPto a new PBWP, activate an SBWP, deactivate an SBWP, or switch an SBWPto a new SBWP, for example, based on one or more fields of one or moreDCIs. Blind decoding complexity and implementation cost of the wirelessdevice may be reduced, and multiple active BWPs may be flexiblysupported. A base station and/or a wireless device may support, forexample, a PBWP and at most one SBWP of a plurality of BWPs. Supportingthe PBWP and the at most one SBWP, compared with one single active BWPin a cell, may improve spectrum efficiency and maintain an acceptablelevel of implementation complexity of the base station and/or thewireless device.

A base station may send (e.g., transmit) one or more DCIs indicating aPBWP switching, an SBWP activation, and/or a PDSCH scheduling on a PBWPor on an SBWP, for example, based on at least one of: one or more valuesof one or more fields of the one or more DCIs; and/or whether the one ormore DCIs are transmitted via a PBWP or an SBWP. The one or more DCIsmay be sent, for example, if a PBWP and at most one SBWP of a pluralityof DL BWPs are supported. Activation of an SBWP may comprisedeactivating a first SBWP and activating a first inactive BWP as an SBWP(e.g., at a time). Activation of an SBWP may comprise activating a firstinactive BWP as an SBWP (e.g., if there is no SBWP before theactivating).

A base station may send (e.g., transmit) one or more DCIs indicating aPBWP switching, for example, if a PBWP and at most one SBWP of aplurality of BWPs are supported. The base station may send the one ormore DCIs indicating the PBWP switching based on at least one of: theBWP indicator indicating a first BWP different from the PBWP and fromthe SBWP; the one or more DCIs being transmitted via the PBWP; and/orone or more value of the first field and/or the second field beingdifferent from a first value (e.g., all zeros) and/or a second value(e.g., all ones). The first value and/or the second value may bepredefined (e.g., fixed).

A base station may send (e.g., transmit) one or more DCIs indicating anSBWP activation, for example, if a PBWP and at most one SBWP of aplurality of BWPs are supported. The base station may send the one ormore DCIs indicating the SBWP activation based on at least one of: theBWP indicator indicating a BWP different from the PBWP (e.g., if thereis no SBWP in the cell); the BWP indicator indicating the BWP differentfrom the SBWP; the one or more DCIs being transmitted via the PBWP; theone or more DCIs being transmitted via the SBWP; one or more value ofthe first field and/or the second field being the first value (e.g., allzeros); and/or the value of the first field or the second field beingthe second value (e.g., all ones).

The wireless device may receive a DL assignment on (e.g., sent via) aPBWP (e.g., without PBWP switching), for example, based on the BWPindicator indicating the PBWP. The wireless device may receive a DLassignment on (e.g., sent via) an SBWP (e.g., without SBWPswitching/activation), for example, based on the BWP indicatorindicating the SBWP. The wireless device may receive one or more DL datapackets from a first PDSCH on the PBWP, for example, after or inresponse to receiving the DL assignment on the PBWP. The wireless devicemay receive one or more DL data packets from a second PDSCH on the SBWP,for example, after or in response to receiving the DL assignment on theSBWP. Blind decoding complexity and implementation cost of the wirelessdevice may be reduced, and a PBWP and at most one SBWP may be flexiblysupported, for example, based on the one or more configurations.

A base station may send (e.g., transmit), to a wireless device, a MAC CEto activate or deactivate an SBWP, for example, if an SBWP activation ordeactivation is not urgent (e.g., not time sensitive). The base stationmay send (e.g., transmit) DCI to switch from a first PBWP to a secondBWP as a second PBWP and/or to switch from a first SBWP to a third BWPas a second SBWP. The base station may send the DCI to switch a BWP, forexample, if BWP switching is urgent (e.g., time sensitive, such as forURLLC).

FIG. 27A, FIG. 27B, FIG. 27C, and FIG. 27D show examples of a MAC CE anda corresponding MAC subheader for one or more SBWPs (or one or morePBWPs) activation/deactivation. FIG. 27A shows an example of the MAC CEcomprising at least one of: one or more first fields indicatingactivation or deactivation of one or more DL BWPs; and/or one or moresecond fields indicating activation or deactivation of one or more ULBWPs. The one or more first fields may comprise a quantity of bits(e.g., D4, D3, D2, and D1 for four bits associated with four DL BWPs,respectively). Di may indicate activation/deactivation (e.g., activationor deactivation) of the DL BWP associated with DL BWP ID=i (e.g., i=1,2, 3, and 4). As shown in FIG. 27A, Di (i=1, 2, 3, and 4) may correspondto four most significant bits of an octet 2 (Oct 2). The Oct 2 maycomprise 8 bits and each of the 8 bits may be associated with an index(e.g., index k=0, 1, 2, 3, 4, 5, 6, and 7). k may be i+3, for example,if Di (i=1, 2, 3, and 4) corresponds to four most significant bits ofthe Oct 2 identified by the indexes (k=4, 5, 6, and 7). Each of thenumber of bits may indicate activation of a corresponding DL BWP, forexample, based on the bit being set to a first value (e.g., 1). Each ofthe number of bits may indicate deactivation of a corresponding DL BWP,for example, based on the bit being set to a second value (e.g., 0). D4being set to the first value may indicate a DL BWP associated with a BWPID 4 is activated if the DL BWP is configured. D4 being set to thesecond value may indicate the DL BWP associated with the BWP ID 4 isdeactivated if the DL BWP is configured. The wireless device may ignorethe value of D4, for example, if the DL BWP associated with the BWP ID 4is not configured. The wireless device may activate/deactivate a DL BWPassociated with a BWP ID 3 based on a value of D3, for example, if theDL BWP associated with the BWP ID 3 is configured. The wireless devicemay activate/deactivate a DL BWP associated with a BWP ID 2 based on avalue of D2, for example, if the DL BWP associated with the BWP ID 2 isconfigured. The wireless device may activate/deactivate a DL BWPassociated with a BWP ID 1 based on a value of D1, for example, if theDL BWP associated with the BWP ID 1 is configured. An RRC message mayindicate an association between a DL BWP and a BWP ID (e.g., the mappingrelationships between the BWP ID 1 and a first DL BWP, between the BWPID 2 and a second DL BWP, between the BWP ID 3 and a third DL BWP,and/or between the BWP ID 4 and a fourth DL BWP). An RRC message may notuse the indexes i, j and/or k. The RRC message may indicate that thefour DL BWPs and/or the four UL BWPs are associated with one of theeight indexes (e.g., the index k).

The one or more second fields may comprise a quantity of bits (e.g., U4,U3, U2, and U1 for 4 bits associated with four UL BWPs, respectively).Uj may indicate activation/deactivation (e.g., activation ordeactivation) of the UL BWP associated with UL BWP ID=j (e.g., j=1, 2,3, and 4). As shown in FIG. 27A, Uj (j=1, 2, 3, and 4) may correspond tofour least significant bits of the Oct 2. k may be j−1, for example, ifUj (j=1, 2, 3, and 4) corresponds to four least significant bits of theOct 2 identified by the indexes (k=0, 1, 2, and 3). Each of the numberof bits may indicate activation of a corresponding UL BWP, for example,based on the bit being set to a first value (e.g., 1), if the UL BWP isconfigured. Each of the number of bits may indicate deactivation of acorresponding UL BWP, for example, based on the bit being set to asecond value (e.g., 0), if the UL BWP is configured. The wireless devicemay ignore the value of Uj, for example, if the UL BWP associated withthe UL BWP ID j is not configured.

FIG. 27B shows an example of the MAC CE comprising at least one of: oneor more first fields indicating activation or deactivation of one ormore DL BWPs; and/or one or more second fields indicating activation ordeactivation of one or more UL BWPs. The configuration shown in FIG. 27Bis similar to the configuration shown in FIG. 27A, for example, exceptthat Uj (j=1, 2, 3, and 4) corresponds to four most significant bits ofthe Oct 2 identified by the indexes (k=4, 5, 6, and 7) and that Di (i=1,2, 3, and 4) corresponds to four least significant bits of the Oct 2identified by the indexes (k=0, 1, 2, and 3). k may be j+3, and k may bei−1.

FIG. 27C shows an example of the MAC CE comprising at least one of: oneor more first fields indicating activation or deactivation of one ormore DL BWPs; and/or one or more second fields indicating activation ordeactivation of one or more UL BWPs. The configuration shown in FIG. 27Cis similar to the configuration shown in FIG. 27A, for example, exceptthat Uj (j=1, 2, 3, and 4) corresponds to four odd-numbered bits of theOct 2 identified by the indexes (k=1, 3, 5, and 7) and that Di (i=1, 2,3, and 4) corresponds to four even-numbered bits of the Oct 2 identifiedby the indexes (k=0, 2, 4, and 6). k may be 2j−1, and/or k may be 2i−2.Also or alternatively, Uj (j=1, 2, 3, and 4) may correspond to foureven-numbered bits of the Oct 2 identified by the indexes (k=0, 2, 4,and 6) and Di (i=1, 2, 3, and 4) may correspond to four odd-numberedbits of the Oct 2 identified by the indexes (k=1, 3, 5, and 7). k may be2j−2, and/or k may be 2i−1. A base station and/or a wireless device maydynamically use the eight bits of the Oct 2. The four most significantbits may be used for other purposes or may be reserved, for example, ifthe wireless device is configured with two DL BWPs (e.g., DL BWPsassociated with D1 and D2) and with two UL BWPs (e.g., UL BWPsassociated with U1 and U2). Two least significant bits (e.g., associatedwith D1 and U1) may always have the first value (e.g., 1), for example,a primary DL BWP and a primary UL BWP are designated (e.g.,semi-statically). The two least significant bits may always have thefirst value (e.g., 1), for example, for the configurations of FIGS. 26A,26B, and 26C (e.g., the primary DL BWP and the primary UL BWP areunswitchable).

FIG. 27D shows an example of the MAC subheader for BWPactivation/deactivation. The MAC subheader may comprise at least one of:a reserved field; a flag field; an LCID field with a first valueindicating the MAC CE for BWP activation/deactivation; and/or a lengthfield. The LCID field may indicate the first value different from otherLCID values (e.g., other LCID values as shown in FIG. 18 and/or FIG.19). The MAC subheader may not comprise the length field, for example,based on the MAC CE for SBWP activation/deactivation having a fixed bitlength.

The base station may send (e.g., transmit) one or more DCIs to switchfrom a first PBWP to a second BWP as a second PBWP or switch from afirst SBWP to a third BWP as a second SBWP, for example, if one or moreMAC CEs are used for activating/deactivating one or more SBWPs. The basestation may send the one or more DCIs to switch from the first PBWP tothe second BWP or switch from the first SBWP to the third BWP, forexample, based on at least one of: one or more values of one or morefields of the one or more DCIs; and/or whether the one or more DCIs aretransmitted on a PBWP or an SBWP.

The wireless device may switch the PBWP to a first BWP as a new PBWPindicated (e.g., identified) by the BWP indicator, for example, based onat least one of: the one or more DCIs being transmitted on the PBWP;and/or the BWP indicator indicating the first BWP different from thePBWP and from the SBWP (e.g., if configured). The wireless device mayswitch the SBWP to a second BWP as a new SBWP indicated (e.g.,identified) by the BWP indicator, for example, based on at least one of:the one or more DCIs being transmitted on the SBWP; and/or the BWPindicator indicating the second BWP different from the PBWP and from theSBWP.

The wireless device may receive a DL assignment on (e.g., sent via) aPBWP (e.g., without PBWP switching), for example, after or in responseto the BWP indicator indicating the PBWP. The wireless device mayreceive a DL assignment on (e.g., sent via) an SBWP (e.g., without SBWPswitching/activation), for example, after or in response to the BWPindicator indicating the SBWP. The wireless device may receive one ormore DL data packets from a first PDSCH mapped on the PBWP, for example,after or in response to receiving the DL assignment via the PBWP. Thewireless device may receive one or more DL data packets from a secondPDSCH mapped on the SBWP, for example, after or in response to receivingthe DL assignment via the SBWP.

A base station may send (e.g., transmit) one or more DCIs indicating aPBWP switching or a PDSCH scheduling on a PBWP or on an SBWP, forexample, if the PBWP and at most one SBWP of a plurality of BWPs aresupported and/or one or more MAC CEs are used foractivating/deactivating an SBWP. The base station may send the one ormore DCIs indicating the PBWP switching or the PDSCH scheduling on thePBWP or on the SBWP, for example, based on a BWP indicator. The wirelessdevice may switch the PBWP to a first BWP as a new PBWP indicated (e.g.,identified) by the BWP indicator, for example, based on the BWPindicator indicating the first BWP different from the PBWP and from theSBWP (e.g., if configured). The wireless device may receive a DLassignment on (e.g., sent via) a PBWP (e.g., without PBWP switching),for example, after or in response to the BWP indicator indicating thePBWP. The wireless device may receive a DL assignment on (e.g., sentvia) an SBWP (e.g., without SBWP switching/activation), for example,after or in response to the BWP indicator indicating the SBWP. Thewireless device may receive one or more DL data packets from a firstPDSCH mapped on the PBWP, after or in response to receiving the DLassignment via the PBWP. The wireless device may receive one or more DLdata packets from a second PDSCH mapped on the SBWP, for example, afteror in response to receiving the DL assignment via the SBWP. CombiningMAC CE for SBWP activation/deactivation and DCI for PBWP/SBWP switchingmay reduce blind decoding complexity and dynamical signaling overhead(e.g., DCI for SBWP activation/deactivation) to support multiple activeBWPs in a cell.

One or more MAC CEs for SBWP activation/deactivation may introduceintolerant transition latency (e.g., scheduling the MAC CE in PDSCHresources and sending one or more HARQ feedback for the MAC CE inPUCCH/PUSCH resources) for some services (e.g., URLLC services). Awireless device may receive multiple types of services, at least some ofwhich may require a quick SBWP activation/deactivation. The transitionlatency may be reduced and/or avoided by introducing a first DCI format,different from one or more other (e.g., existing) DCI formats (e.g., DCIformat 1_0/1_1). The first DCI format may comprise one or more fieldsindicating a PBWP switching, an SBWP activation, an SBWP deactivation,and/or an SBWP switching based on one or more values of the one or morefields of the first DCI format. The first DCI format may comprise atleast one of: a BWP indicator; and/or a second field (e.g., BWPaction/mode indication) indicating one of a PBWP switching, an SBWPactivation, an SBWP deactivation, and/or an SBWP switching.

FIG. 28A shows an example of a first DCI format comprising a BWP IDfield and a second field. The second field may be an action indicationfield (e.g., a field indicating an action associated with a BWPindicated by the BWP ID field). A wireless device may switch a PBWP to afirst BWP as a new PBWP, for example, if the wireless device receivesone or more DCIs based on the first DCI format. The wireless device mayswitch the PBWP to the first BWP, for example, based on at least one of:the BWP indicator (e.g., a BWP ID in the BWP ID field) indicating thefirst BWP; the first BWP being different from the PBWP; and/or thesecond field being set to a first value (e.g., “00” if a size of thesecond field corresponds to two bits). The wireless device may receive aDL assignment on (e.g., sent via) a PBWP (e.g., without PBWP switching),for example, based on the BWP indicator indicating the PBWP and/or thesecond field being set to the first value (e.g., “00”).

The wireless device may activate a second BWP as an SBWP, for example,if the wireless device receives the one or more DCIs based on the firstDCI format. The wireless device may activate the second BWP, forexample, based on at least one of: the BWP indicator indicating thesecond BWP; and/or the second field being set to a second value (e.g.,“01” if the size of the second field corresponds to two bits).

The wireless device may deactivate an SBWP, for example, if the wirelessdevice receives the one or more DCIs based on the first DCI format. Thewireless device may deactivate the SBWP, for example, based on at leastone of: the BWP indicator indicating the SBWP; and the second fieldbeing set to a third value (e.g., “10”).

The wireless device may switch an SBWP to a third BWP, for example, ifthe wireless device receives the one or more DCIs based on the first DCIformat. The wireless device may switch the SBWP to the third BWP, forexample, based on at least one of: the BWP indicator indicating thethird BWP; the third BWP being different from the PBWP and from theSBWP; and/or the second field being set to a fourth value (e.g., “11” ifthe size of the second field corresponds to two bits). The wirelessdevice may receive a DL assignment on (e.g., sent via) an SBWP (e.g.,without SBWP switching), for example, after or in response to the BWPindicator indicating the SBWP and/or the second field being set to thefourth value (e.g., “11”).

A base station may send (e.g., transmit) first DCI based on an existingDCI format (e.g., DCI format 1_0/1_1) indicating PBWP/SBWP switchingand/or indicating a DL scheduling on the PBWP/SBWP. A base station maysend (e.g., transmit) second DCI based on second DCI format (e.g.,different from the existing DCI format) indicating SBWPactivation/deactivation. The second DCI format may comprise at least oneof: a BWP indicator; and/or a second field indicating activation ordeactivation of an SBWP.

FIG. 28B shows an example DCI format comprising a BWP ID field and asecond field. A wireless device may switch from the PBWP to a first BWPas a new PBWP, for example, if the wireless device receives the firstDCI based on a particular DCI format (e.g., an existing DCI format, suchas DCI format 1_0/1_1, or any other DCI format). The wireless device mayreceive first DCI, for example, based on the BWP indicator indicatingthe first BWP different from the PBWP and/or first DCI being transmittedvia the PBWP. The wireless device may receive a DL assignment on (e.g.,sent via) the PBWP, for example, after or in response to the BWPindicator indicating the PBWP.

A wireless device may switch from the SBWP to a second BWP as a newSBWP, for example, if the wireless device receives first DCI based on aparticular DCI format (e.g., an existing DCI format such as DCI format1_0/1_1, or any other DCI format). The wireless device may receive thefirst DCI, for example, based on the BWP indicator indicating the secondBWP different from the SBWP and/or the first DCI being transmitted viathe SBWP. The wireless device may receive a DL assignment on (e.g., sentvia) the SBWP, for example, after or in response to the BWP indicatorindicate the SBWP.

A wireless device may activate a third BWP indicated by the BWPindicator as a second SBWP, for example, if the wireless device receivesthe second DCI based on the second DCI format (e.g., different from DCIformat 1_0/1_1). The wireless device may activate the third BWP, forexample, based on the second field of the second DCI being a first value(e.g., “1” if a size of the second fields corresponds to one bit).

A wireless device may deactivate the SBWP indicated by the BWPindicator, for example, if the wireless device receives the second DCIbased on the second DCI format (e.g., different from DCI format1_0/1_1). The wireless device may deactivate the SBWP, for example,based on the second field of the second DCI being a second value (e.g.,“0”).

A base station may send (e.g., transmit) DCI based on a third DCI format(e.g., different from an existing format such as DCI format 1_0/1_1, orany other DCI format) indicating a PBWP switching or an SBWP activation,for example, if at most one SBWP is supported. The third DCI format maycomprise at least one of: a BWP indicator; and/or a second fieldindicating a PBWP switching or an SBWP activation. The PBWP switching orthe SBWP activation may be indicated based on a value of the secondfield. Activation of a BWP as a new SBWP may deactivate an active SBWPand activate the BWP as the new SBWP (e.g., at a time), for example, ifat most one SBWP is supported.

A base station may send (e.g., transmit) the DCI based on the third DCIformat to a wireless device. The wireless device may switch from thePBWP to a first BWP indicated by the BWP indicator, as a new PBWP, forexample, if the wireless device receives the DCI and at most one SBWP issupported. The wireless device may switch from the PBWP to the firstBWP, for example, based on the second field being a first value (e.g.,“1” if a size of the second field corresponds to one bit). The wirelessdevice may receive a DL assignment on (e.g., sent via) the PBWP, forexample, if the BWP indicator indicates the PBWP.

The wireless device may activate a second BWP indicated by the BWPindicator, as a new SBWP, for example, if the wireless device receivesthe DCI based on the third DCI format and at most one SBWP is supported.The wireless device may activate the second BWP, for example, based onthe second field being a second value (e.g., “0” if a size of the secondfield corresponds to one bit). The wireless device may deactivate afirst SBWP (e.g., if the first SBWP is configured and in active state),for example, after or in response to activating the second BWP. Thewireless device may receive a DL assignment on (e.g., sent via) theSBWP, for example, if the BWP indicator indicates the SBWP.

A base station may send (e.g., transmit) one or more DCIs (e.g., DCIformat 1_0/1_1), to a wireless device, indicating an SBWP activation, anSBWP deactivation, or an SBWP switching, for example, based on at leastone of: one or more values of one or more fields of the one or moreDCIs; and/or whether the one or more DCIs are transmitted via a PBWP orvia an SBWP. The one or more DCIs may be transmitted based on DCI format1_0 or 1_1 indicating a PDSCH scheduling. The one or more fields maycomprise at least one of: a carrier indicator; an identifier for a DCIformat; a BWP indicator; a first field indicating a frequency domainresource assignment; a second field indicating a time domain resourceassignment; a PUCCH resource indicator; a TPC command for a scheduledPUCCH; and/or a PDSCH-to-HARQ_feedback timing indicator. Reusing anexisting DCI format (e.g., DCI format 1_0 or 1_1) for a BWP operationsupporting multiple active BWPs may reduce blind decoding complexity ata wireless device. A PBWP may be in active state, for example, at leastuntil receiving an RRC message.

The wireless device may switch the SBWP to a first BWP as a new SBWPindicated (e.g., identified) by the BWP indicator, for example, based onat least one of: the one or more DCIs being transmitted via the SBWP;the BWP indicator indicating the first BWP different from the PBWP andfrom the SBWP; a value of the first field or the second field beingdifferent from a first value (e.g., all zeros); and/or the value of thefirst field or the second field being different from a second value(e.g., all ones). The first value and/or the second value may bepredefined (e.g., fixed).

The wireless device may activate a second BWP as a new SBWP indicated(e.g., identified) by the BWP indicator, for example, based on at leastone of: the BWP indicator indicating the second BWP different from thePBWP and from the SBWP; and/or the value of the first field or thesecond field being the first value (e.g., all zeros). The wirelessdevice may deactivate the SBWP, for example, based on at least one of:the one or more DCIs being transmitted via the PBWP; the BWP indicatorindicating the SBWP different from the PBWP; and/or the value of thefirst field or the second field being the second value (e.g., all ones).

The wireless device may receive a DL assignment on (e.g., sent via) aPBWP, for example, based on the BWP indicator indicating the PBWP. Thewireless device may receive a DL assignment on (e.g., sent via) an SBWP(e.g., without SBWP switching/activation/deactivation), for example,based on the BWP indicator indicating the SBWP. The wireless device mayreceive one or more DL data packets from a first PDSCH mapped on thePBWP, for example, after or in response to receiving the DL assignmentvia the PBWP. The wireless device may receive one or more DL datapackets from a second PDSCH mapped on the SBWP, for example, after or inresponse to receiving the DL assignment via the SBWP.

The base station and the wireless device may dynamically activate anSBWP, deactivate an SBWP, and/or switch an SBWP to a new SBWP, forexample, based on one or more fields of one or more DCIs. Transitionlatency and/or implementation cost of the wireless device may bereduced, and/or multiple active BWPs may be flexibly supported.

A base station may send (e.g., transmit) one or more DCIs indicating anSBWP activation, for example, if a PBWP and at most one SBWP aresupported. The base station may send the one or more DCIS indicating theSBWP activation, for example, based on at least one of: the BWPindicator indicating a BWP different from the PBWP (e.g., if there is noSBWP in the cell); the BWP indicator indicating the BWP different fromthe SBWP; the one or more DCIs being transmitted via the PBWP; and/orthe one or more DCIs being transmitted via the SBWP.

Activation of an SBWP may comprise deactivating a first SBWP andactivating a first inactive BWP as the SBWP (e.g., at a time).Activation of an SBWP may comprise activating a first inactive BWP asthe SBWP, for example, if there is no active SBWP before the activating.

The wireless device may receive a DL assignment via a PBWP (e.g.,without PBWP switching), for example, based on the BWP indicatorindicating the PBWP. The wireless device may receive a DL assignment viaan SBWP (e.g., without SBWP switching/activation), for example, based onthe BWP indicator indicating the SBWP. The wireless device may receiveone or more DL data packets from a first PDSCH via the PBWP, forexample, after or in response to receiving the DL assignment via thePBWP. The wireless device may receive one or more DL data packets from asecond PDSCH via the SBWP, for example, after or in response toreceiving the DL assignment via the SBWP. Blind decoding complexityand/or implementation cost of the wireless device may be reduced, and/ora PBWP and an SBWP (e.g., at most one SBWP) may be flexibly supported.

A base station may send (e.g., transmit), to a wireless device, a MAC CEto activate or deactivate an SBWP, for example, if an SBWP activation ordeactivation is not urgent (or time sensitive). The base station maysend (e.g., transmit) DCI to switch from a first SBWP to a second BWP asa second SBWP, for example, if a PBWP is in an active state untilswitched by an RRC message. FIG. 27A, FIG. 27B, FIG. 27C, and FIG. 27Dshow examples of a MAC CE and a corresponding MAC subheader for one ormore SBWP activation/deactivation.

The base station may send (e.g., transmit) one or more DCIs (e.g., DCIformat 1_0/1_1) to switch from a first SBWP to a second BWP as a secondSBWP, for example, if one or more MAC CEs are used foractivating/deactivating an SBWP and the PBWP is always in active stateuntil switched by an RRC message. The base station may send the one ormore DCIs to switch from the first SBWP to the second BWP, for example,based on at least one of: one or more values of one or more fields ofthe one or more DCIs; and/or whether the one or more DCIs aretransmitted via a PBWP or via an SBWP. The wireless device may switch afirst SBWP to a second BWP as a second SBWP indicated (e.g., identified)by the BWP indicator, for example, based on at least one of: the one ormore DCIs being transmitted via the first SBWP; and/or the BWP indicatorindicating the second BWP different from the PBWP and from the firstSBWP.

The wireless device may receive a DL assignment via a PBWP, for example,based on the BWP indicator indicating the PBWP. The wireless device mayreceive a DL assignment via an SBWP (e.g., without SBWP switching), forexample, based on the BWP indicator indicating the SBWP. The wirelessdevice may receive one or more DL data packets from a first PDSCH viathe PBWP, for example, after or in response to receiving the DLassignment via the PBWP. The wireless device may receive one or more DLdata packets from a second PDSCH via the SBWP, for example, after or inresponse to receiving the DL assignment via the SBWP.

A base station may send (e.g., transmit) one or more DCIs indicating aPDSCH scheduling on a PBWP or an SBWP, for example, if a PBWP and atmost one SBWP of a plurality of BWPs are supported and one or more MACCEs are used for activating/deactivating an SBWP. The base station maysend the one or more DCIs indicating the PDSCH scheduling, for example,based on a BWP indicator of the one or more DCIs. The wireless devicemay receive a DL assignment via a PBWP, for example, based on the BWPindicator indicating the PBWP. The wireless device may receive a DLassignment via an SBWP (e.g., without SBWP switching/activation), forexample, based on the BWP indicator indicating the SBWP. The wirelessdevice may receive one or more DL data packets from a first PDSCH viathe PBWP, for example, after or in response to receiving the DLassignment via the PBWP. The wireless device may receive one or more DLdata packets from a second PDSCH via the SBWP, for example, after or inresponse to receiving the DL assignment via the SBWP.

A wireless device may perform SBWP switching based on the one or moreMAC CEs. A base station may send (e.g., transmit) the one or more MACCEs indicating an activation of a second SBWP and/or a deactivation of afirst SBWP, for example, by setting a second field of the one or morefirst fields corresponding the second SBWP to a first value (e.g., “1”)and/or setting a first field of the one or more first fieldscorresponding to the first SBWP to a second value (e.g., “0”). Thewireless device may switch from the first SBWP to the second SBWP, forexample, after or in response to receiving the one or more MAC CEs.Combining MAC CE for SBWP activation/deactivation and DCI for SBWPswitching may reduce blind decoding complexity and/or dynamic signalingoverhead (e.g., DCI for SBWP activation/deactivation) to supportmultiple active BWPs in a cell.

One or more MAC CEs for SBWP activation/deactivation may introduceintolerant transition latency (e.g., which may be caused by schedulingthe MAC CE in PDSCH resources at a base station and sending one or moreHARQ feedbacks for the MAC CE in PUCCH/PUSCH resources at a wirelessdevice) for some services (e.g., URLLC). A wireless device may receivemultiple types of services, which may require a quick SBWPactivation/deactivation. The transition latency may be reduced, forexample, by introducing a first DCI format, which may be different fromone or more other DCI formats (e.g., an existing DCI format such as DCIformat 1_0/1_1, or any other DCI format). The first DCI format maycomprise one or more fields indicating SBWPactivation/deactivation/switching based on one or more values of the oneor more fields of the first DCI format. The first DCI format maycomprise at least one of: a BWP indicator; a second field (e.g., BWPaction/mode indication) indicating one of SBWP activation, SBWPdeactivation, and/or SBWP switching, for example, if a PBWP is in activestate until switched/deactivated by an RRC message.

FIG. 29A shows an example of a first DCI format comprising a BWP IDfield and an action indication field (e.g., a second field forindicating a change of a BWP). A wireless device may receive a DLassignment via a PBWP, for example, if the wireless device receives oneor more DCIs based on the first DCI format. The wireless device mayreceive the DL assignment via the PBWP, for example, based on a BWPindicator indicating the PBWP and/or the second field being set to afirst value (e.g., “00” if a size of the second field corresponds to twobits). A wireless device may receive a DL assignment via an SBWP, forexample, if the wireless device receives one or more DCIs based on thefirst DCI format. The wireless device may receive the DL assignment viathe SBWP, for example, based on the BWP indicator indicating the SBWPand/or the second field being set to a first value (e.g., “00”).

The wireless device may activate a first BWP as an SBWP, for example, ifthe wireless device receives the one or more DCIs based on the first DCIformat. The wireless device may activate the first BWP as an SBWP, forexample, based on at least one of: the BWP indicator indicating thefirst BWP; and/or the second field being set to a second value (e.g.,“01” if a size of the second field corresponds to two bits).

The wireless device may deactivate an SBWP, for example, if the wirelessdevice receives the one or more DCIs based on the first DCI format. Thewireless device may deactivate the SBWP, for example, based on at leastone of: the BWP indicator indicating the SBWP; and the second fieldbeing set to a third value (e.g., “10”).

The wireless device may switch an SBWP to a second BWP, for example, ifthe wireless device receives the one or more DCIs based on the first DCIformat. The wireless device may switch the SBWP to the second BWP, forexample, based on at least one of: the BWP indicator indicating thesecond BWP; the second BWP being different from the PBWP and from theSBWP; and/or the second field being set to a fourth value (e.g., “11”).

FIG. 29B shows an example of second DCI format comprising a BWP ID fieldand an action indication field (e.g., a second field for indicating achange of a BWP). A base station may send (e.g., transmit) first DCIbased on a DCI format (e.g., an existing DCI format such as DCI format1_0/1_1, or any other DCI format) indicating SBWP switching, or DLscheduling on the PBWP/SBWP. A base station may send (e.g., transmit)second DCI based on the second DCI format (e.g., different from theexisting DCI format, such as DCI format 1_0/1_1, or any other DCIformat) indicating SBWP activation/deactivation. The second DCI formatmay comprise at least one of: a BWP indicator; and/or a second fieldindicating activation or deactivation of an SBWP.

A wireless device may switch from the SBWP to a first BWP as a new SBWP,for example, if the wireless device receives the first DCI based on theDCI format (e.g., an existing such as DCI format 1_0/1_1, or any otherDCI format). The wireless device may switch from the SBWP to the firstBWP, for example, based on the BWP indicator indicating the first BWPdifferent from the SBWP and/or the first DCI being transmitted via theSBWP.

A wireless device may activate a second BWP indicated by the BWPindicator as a second SBWP, for example, if the wireless device receivesthe second DCI based on the second DCI format (e.g., different from DCIformat 1_0/1_1 or another DCI format). The wireless device may activatethe second BWP as the second SBWP, for example, based on the secondfield of the second DCI being a first value (e.g., “1” if a size of thesecond field corresponds to one bit). A wireless device may deactivatethe SBWP indicated by the BWP indicator, for example, if the wirelessdevice receives the second DCI based on the second DCI format (e.g.,different from DCI format 1_0/1_1 or another DCI format). The wirelessdevice may deactivate the SBWP indicated by the BWP indicator, forexample, based on the second field of the second DCI being a secondvalue (e.g., “0”).

A base station may send (e.g., transmit) DCI based on a DCI format(e.g., an existing DCI format such as DCI format 1_0/1_1, or any otherDCI format) indicating an SBWP activation, for example, if at most oneSBWP is supported. A wireless device may activate a first BWP as asecond SBWP, for example, based on the BWP indicator indicating thefirst BWP is different from a first SBWP and from the PBWP. Theactivating the first BWP as the second SBWP may comprise deactivatingthe first SBWP and activating the first BWP as the second SBWP (e.g., ata time), for example, if at most one SBWP is supported and the PBWP isin active state at least until switched/deactivated by an RRC message.The activating the first BWP as the second SBWP may comprise activatingthe first BWP as the second SBWP, for example, if there is no SBWPbefore the activating and/or if at most one SBWP is supported and thePBWP is in an active state at least until switched/deactivated by an RRCmessage.

A wireless device may support a plurality of active BWPs in a cell, forexample, if a determination of a PBWP or an SBWP of the plurality ofactive BWPs is not performed. A base station may send (e.g., transmit)one or more DCIs indicating an active BWP switching, a BWP activation, aBWP deactivation, or a PDSCH scheduling on the active BWP, for example,based on at least one of: one or more values of one or more fields ofthe one or more DCIs. The one or more DCIs may be sent (e.g.,transmitted) based on a DCI format (e.g., DCI format 1_0 or 1_1, or anyother DCI format) indicating a PDSCH scheduling. The one or more fieldsmay comprise at least one of: a carrier indicator; an identifier for aDCI format; a BWP indicator; a first field indicating a frequency domainresource assignment; a second field indicating a time domain resourceassignment; a PUCCH resource indicator; a TPC command for scheduledPUCCH; and/or a PDSCH-to-HARQ_feedback timing indicator. Reusing a DCIformat (e.g., an existing DCI format such as DCI format 1_0 or 1_1, orany other DCI format) for a BWP operation supporting multiple activeBWPs may reduce blind decoding complexity at a wireless device.

A wireless device (e.g., with active BWPs in active state) may switchfrom a first active BWP to a second BWP indicated (e.g., identified) bythe BWP indicator, for example, based on at least one of: the one ormore DCIs being transmitted via the first active BWP; the BWP indicatorindicating the second BWP different from the active BWPs; one or morevalues of the first field and/or the second field being different from afirst value (e.g., all zeros); and/or the value of the first field orthe second field being different from a second value (e.g., all ones).

A wireless device (e.g., tith active BWPs in active state) may activatea third BWP indicated (e.g., identified) by the BWP indicator, forexample, based on at least one of: the BWP indicator indicating thethird BWP different from the active BWPs; and/or the value of the firstfield or the second field being the first value (e.g., all zeros). Awireless device (e.g., with active BWPs in active state) may deactivatean active BWP, for example, based on at least one of: the BWP indicatorindicating the active BWP; and/or the value of the first field or thesecond field being the second value (e.g., all ones).

A wireless device may receive a DL assignment via an active BWP (e.g.,without active BWP switching), for example, based on at least one of:the BWP indicator indicating the active BWP; the value of the firstfield or the second field not being the first value (e.g., all zeros);and/or the value of the first field or the second field not being thesecond value (e.g., all ones). The wireless device may receive one ormore DL data packets from a PDSCH via the active BWP, for example, afteror in response to receiving the DL assignment via the active BWP.

A base station and/or a wireless device may dynamicallyswitch/activate/deactivate a BWP based on one or more fields of one ormore DCIs. Blind decoding complexity and implementation cost of thewireless device may be reduced and/or multiple active BWPs may beflexibly supported.

A wireless device may support a plurality of active BWPs in a cell, forexample, if a determination of a PBWP or an SBWP of the plurality ofactive BWPs is not performed. A base station may send (e.g., transmit),to a wireless device, a MAC CE to activate or deactivate a BWP, forexample, if BWP activation or deactivation is not urgent (e.g., not timesensitive). The base station may send (e.g., transmit) DCI to switchfrom a first active BWP to a second BWP as a second active BWP. FIG.27A, FIG. 27B, FIG. 27C, and FIG. 27D show examples of a MAC CE and acorresponding MAC subheader for one or more BWP activation/deactivation.

A wireless device (e.g., with active BWPs in active state) may switchfrom a first active BWP to a second BWP indicated (e.g., identified) bythe BWP indicator, for example, based on at least one of: the BWPindicator indicating the second BWP different from the active BWPs;and/or the DCI being transmitted via the first active BWP. A wirelessdevice may receive a DL assignment via an active BWP (e.g., withoutactive BWP switching), for example, based on the BWP indicatorindicating the active BWP. A wireless device may receive one or more DLdata packets from a PDSCH via the active BWP, for example, after or inresponse to receiving the DL assignment via the active BWP.

A wireless device may support a plurality of active BWPs in a cell, forexample, if a determination of a PBWP or an SBWP of the plurality ofactive BWPs is not performed. One or more MAC CEs for SBWPactivation/deactivation may introduce intolerant transition latency(e.g., caused by scheduling the MAC CE in PDSCH resources and sendingone or more HARQ feedbacks for the MAC CE in PUCCH/PUSCH resources) forsome services (e.g., URLLC). A wireless device may receive one or moreof multiple types of services, at least some of which may require quickSBWP activation/deactivation. The transition latency by introducing afirst DCI format, different from one or more other DCI formats (e.g., anexisting DCI format such as DCI format 1_0/1_1, or any other DCIformat), may be improved. The first DCI format may comprise one or morefields indicating one of BWP switching, BWP activation, and/or BWPdeactivation, for example, based on one or more values of the one ormore fields of the first DCI format. The first DCI format may compriseat least one of: a BWP indicator; and/or a second field (e.g., BWPaction/mode indication) indicating one of BWP switching, BWP activation,and/or BWP deactivation.

FIG. 30A shows an example of a first DCI format comprising a BWP IDfield and an action indication field (e.g., a second field forindicating a change of a BWP). A wireless device may switch a firstactive BWP to a first BWP as a second active BWP, for example, if thewireless device receives one or more DCIs based on the first DCI formatand multiple BWPs are in active state. The wireless device may switchthe first active BWP to the first BWP, for example, based on at leastone of: the BWP indicator indicating the first BWP; the first BWP beingdifferent from the multiple BWPs; and/or the second field being set to afirst value (e.g., “00” if a size of the second field corresponds to twobits). The wireless device may receive a DL assignment via an active BWP(e.g., without BWP switching), for example, based on the BWP indicatorindicating the active BWP and/or the second field being set to a firstvalue (e.g., “00” if a size of the second field corresponds to twobits).

The wireless device may activate a second BWP as an active BWP, forexample, if the wireless device receives the one or more DCIs based onthe first DCI format and multiple BWPs are in active state. The wirelessdevice may activate the second BWP as an active BWP, for example, basedon at least one of: the BWP indicator indicating the second BWP; and/orthe second field being set to a second value (e.g., “01” if the size ofthe second field corresponds to two bits).

The wireless device may deactivate an active BWP, for example, if thewireless device receives the one or more DCIs based on the first DCIformat and multiple BWPs are in active state. The wireless device maydeactivate the active BWP, for example, based on at least one of: theBWP indicator indicating the active BWP; and the second field being setto a third value (e.g., “10” if the size of the second field correspondsto two bits).

The wireless device may switch a first active BWP to a third BWP, forexample, if the wireless device receives the one or more DCIs based onthe first DCI format and multiple BWPs are in active state. The wirelessdevice may switch the first active BWP to the third BWP, for example,based on at least one of: the BWP indicator indicating the third BWP;the third BWP being different from the multiple BWPs; and/or the secondfield being set to a fourth value (e.g., “11” if the size of the secondfield corresponds to two bits).

FIG. 30B shows an example of a second DCI format comprising a BWP IDfield and an action indication field (e.g., a second field forindicating a change of a BWP). A base station may send (e.g., transmit)first DCI based on a DCI format (e.g., an existing DCI format such asDCI format 1_0/1_1, or any other DCI format) indicating BWP switching,and/or DL scheduling on an active BWP.

A base station may send (e.g., transmit) second DCI based on the secondDCI format (e.g., different from the first DCI format and/or differentfrom an existing DCI format) indicating BWP activation/deactivation. Thesecond DCI format may comprise at least one of: a BWP indicator; and/ora second field indicating activation or deactivation of a BWP.

A wireless device may switch from a first active BWP to a first BWP as asecond active BWP, for example, if the wireless device receives thefirst DCI based on a DCI format (e.g., an existing DCI format such asDCI format 1_0/1_1, or any other DCI format) and multiple BWPs are inactive states. The wireless device may switch from the first active BWPto the first BWP, for example, based on the BWP indicator indicating thefirst BWP different from the multiple active BWPs and/or the first DCIbeing transmitted via the first active BWP. The wireless device mayreceive a DL assignment via the first active BWP, for example, if theBWP indicator indicates the first active BWP.

A wireless device may activate a third BWP indicated by the BWPindicator as a second active BWP, for example, if the wireless devicereceives the second DCI based on the second DCI format (e.g., differentfrom DCI format 1_0/1_1 or another DCI format). The wireless device mayactivate the third BWP as the second active BWP, for example, based onthe second field of the second DCI being a first value (e.g., “1” if asize of the second field corresponds to one bit).

A wireless device may deactivate an active BWP indicated by the BWPindicator, for example, if the wireless device receives the second DCIbased on the second DCI format (e.g., different from DCI format1_0/1_1). The wireless device may deactivate the active BWP, forexample, based on the second field of the second DCI being a secondvalue (e.g., “0” if the size of the second field corresponds to onebit).

FIG. 31 shows an example of a flowchart of changing one or more BWPstates for a configuration of multiple active BWPs. At step 3101, awireless device may receive, from a base station, one or more messagescomprising configuration parameters of BWPs of a cell. The BWPs maycomprise a first active BWP and a second BWP. At step 3102, the wirelessdevice may monitor a PDCCH on (e.g., sent via) the first active BWP. Atstep 3103, the wireless device may detect a DCI. The DCI may comprise afirst field and a second field. The first field may indicate a secondBWP index of the second BWP. The wireless device may perform one ofmultiple BWP operations based on a first value of the first field and/ora second value of the second field. The multiple BWP operations maycomprise at least one of: switching from the first active BWP to asecond BWP; activating the second BWP and maintaining an activationstate of the first active BWP; deactivating the second BWP; switchingfrom the second BWP to a third BWP; and/or receiving DL/UL schedulingassignment via the first active BWP.

Switching to the second BWP may comprise switching an active BWP fromthe primary active BWP to the second BWP and monitoring a PDCCH on(e.g., sent via) the second BWP. The activating the second BWP maycomprise monitoring a PDCCH on the second BWP. The activating the secondBWP may comprise monitoring a PDCCH on (e.g., sent via) the PBWP for thesecond BWP, for example, if the second BWP is configured to be cross-BWPscheduled by the PBWP.

At step 3104, the wireless device may determine whether a first command(e.g., in the DCI) indicates a PBWP switching to a first BWP. At step3105, the wireless device may switch to the first BWP as a new PBWP, forexample, based on the first command indicating a PBWP switching to thefirst BWP. At step 3106, the wireless device may determine whether thefirst command indicates activating a second BWP. At step 3107, thewireless device may switch to the second BWP as a SBWP, for example,based on the first command indicating activating a second BWP. At step3108, the wireless device may determine whether the first commandindicates deactivating a first SBWP. At step 3109, the wireless devicemay deactivate the first SBWP, for example, based on the first commandindicating deactivating the first SBWP. At step 3110, the wirelessdevice may determine whether the first command indicates a SBWPswitching to a third BWP. At step 3111, the wireless device may switchthe SBWP to the third BWP as a new SBWP, for example, based on the firstcommand indicating a SBWP switching to the third BWP. The wirelessdevice may perform any one or more of steps 3104, 3106, 3108, and/or3110, for example, in any order. The wireless device may perform any oneor more of steps 3105, 3107, 3109, and/or 3111, for example, in anyorder.

FIG. 32 shows an example of a procedure at a cell that may be configuredwith a plurality of BWPs. A base station 3202 may transmit one or moremessages, comprising configuration parameters 3212 of a cell, to awireless device 3204. The configuration parameters may correspond to oneor more RRC messages (e.g., one or more of an RRC connection configuredmessage, an RRC connection reestablishment messages, and an RRCconnection setup message, etc.). The configuration parameters 3212 maycomprise a configuration of a plurality of BWPs 3206 of the cell. Theplurality of BWPs may comprise N+1 BWPs: BWP 0, BWP 1, BWP 2 . . . BWPN. The wireless device 3204 may receive the one or more messages at timet₁.

The wireless device 3204 may activate, for example, a first BWP at t₂.The wireless device 3204 may activate, for example, in addition to thefirst BWP, a second BWP at t₂. The first BWP and the second BWP may be,for example, the BWP 1 and the BWP 2, respectively, of the plurality ofBWPs 3206. The wireless device 3204 may activate, for example, more thantwo BWPs of the plurality of BWPs 3206. The wireless device 3204 mayactivate, for example, one or more other BWPs among the plurality ofBWPs 3206 in addition to or instead of the BWP 1 and/or the BWP 2. Thewireless device may activate one or more BWPs of the plurality of BWPs3206, for example, based on the configuration parameters received at t₁.

The base station 3202 may transmit DCI 3214 via a downlink channel, suchas a PDCCH on the first BWP. The DCI 3214 may comprise, for example, aBWP ID field and an action indication field. The action indication fieldmay indicate, based on its contents, one of: a switching of a BWP asindicated in the BWP ID field, an activation of a BWP as indicated inthe BWP ID field, or a deactivation of a BWP as indicated in the BWP IDfield. The action indication field may be, for example, two bits inlength (or any other quantity of bits). The wireless device 3204 mayreceive the DCI at time t₃. The wireless device 3204 may interpret thecontents of the action indication field in the DCI based on a predefinedrule, such as the table 3208. The wireless device 3204 may interpret thecontents of the action indication field via the predefined rule (e.g.,as per the table 3208), for example, if the BWP ID field indicates a BWPdifferent from the first BWP.

The BWP ID field may indicate, for example, a BWP ID corresponding tothe second BWP. The wireless device 3204 may determine, for example, oneof: an activation of the second BWP, a deactivation of the second BWP,and a switch to the second BWP, based on the contents of the actionindication field, at time t₄. The wireless device 3204 may switchoperation to the second BWP, for example, by deactivating the first BWPand activating the second BWP, for example, if contents of the actionindication field indicate a first value (e.g., “00”). The wirelessdevice 3204 may activate the second BWP, for example, if contents of theaction indication field indicate a second value (e.g., “01”). Thewireless device 3204 may deactivate the second BWP, for example, ifcontents of the action indication field indicate a third value (e.g.,“10”). A fourth value (e.g., “11”) may be reserved, for example, forfuture use. The wireless device 3204 may perform UL/DL operations onactive BWPs 3210 as determined at time t₄.

The BWP ID field of DCI may indicate, for example, a BWP IDcorresponding to the BWP 2. Initial active BWPs at t₂ may correspond to,for example, (i) the BWP 1, or (ii) both the BWP 1 and the BWP 2. Theactive BWPs 3210 as determined at time t₄ may depend on the initialactive BWPs at time t₂ and contents of an action indication field of theDCI 3214. The active BWPs 3210 as determined at time Li may correspondto one of: (i) both the BWP 1 and the BWP 2, (ii) the BWP 1, or (iii)the BWP 2. The active BWPs 3210 may correspond to, for example, both theBWP 1 and the BWP 2 if (i) the BWP 1 was activated at time t₂, and (ii)contents of the action indication field indicate activation of the BWP 2(e.g., “01”). The active BWPs 3210 may correspond to, for example, theBWP 1 if (i) both the BWP 1 and the BWP 2 were activated at time t₂, and(ii) contents of the action indication field indicate deactivation ofthe BWP 2 (e.g., “10”). The active BWPs 3210 may correspond to, forexample, the BWP 2 if (i) the BWP 1 was activated at time t₂, and (ii)contents of the action indication field indicates switching of the BWP 1to the BWP 2 (e.g., “00”).

FIG. 33 shows an example method that may be performed by a wirelessdevice to configure a plurality of BWPs. The procedure of FIG. 33 maycorrespond to operations of a wireless device associated with the cell.At step 3302, the wireless device may receive one or more messagescomprising configuration parameters corresponding to the cell. The oneor more messages may comprise one or more RRC messages. Theconfiguration parameters may comprise parameters for one or moreconfigurations of the plurality of BWPs of the cell.

At step 3303, the wireless device may determine whether all active BWPsof the cell are allowed to be switched by DCI. At step 3304, thewireless device may determine that an action indication field of DCI isconfigured with two bits, for example, if the wireless device determinesthat all active BWPs of the cell are allowed to be switched by DCI. Atstep 3306, the wireless device may perform actions based on a two-bitaction indication field of DCI (e.g., actions as described above withreference to FIG. 28A, FIG. 29A, or FIG. 30A), for example, based on thedetermination that the action indication field is configured with twobits. The wireless device may interpret an action indication field ofDCI as described above, for example, with reference to FIG. 28A, FIG.29A, or FIG. 30A.

At step 3307, the wireless device may determine whether at least oneactive BWP of the cell is not allowed to be switched by DCI. At step3308, the wireless device may determine that an action indication fieldof DCI is configured with one bit, for example, if the wireless devicedetermines that at least one active BWP of the cell is not allowed to beswitched by the DCI. At step 3310, the wireless device may performactions based on a one-bit action indication field of DCI (e.g., actionsas described above with reference to FIG. 28B, FIG. 29B, or FIG. 30B),for example, based on the determination that the action indication fieldis configured with one bit. The wireless device may interpret an actionindication field of DCI as described above, for example, with referenceto FIG. 28B, FIG. 29B, or FIG. 30B.

FIG. 34 shows an example method that may be performed by a base stationto configure a plurality of BWPs. The procedure of FIG. 34 maycorrespond to operations of a base station associated with the cell. Atstep 3402, the base station may transmit, to a wireless device, one ormore messages, comprising configuration parameters corresponding to thecell. The one or more messages may comprise one or more RRC messages.The configuration parameters may comprise parameters for one or moreconfigurations of the plurality of BWPs of the cell.

At step 3403, the base station may determine, for a wireless device,whether all active BWPs of the cell are allowed to be switched by DCI.At step 3404, the base station may determine an action indication fieldof DCI to be configured with two bits, for example, if the base stationdetermines that all active BWPs of the cell are allowed to be switchedby the DCI. At step 3406, the base station may transmit, for example,DCI with an action indication field configured with two bits thatindicates actions to be performed by the wireless device (e.g., asdescribed above with reference to FIG. 28A, FIG. 29A, or FIG. 30A).

At step 3407, the base station may determine, for a wireless device,whether at least one active BWP of the cell is not allowed to beswitched by DCI. At step 3408, the base station may determine an actionindication field of DCI to be configured with one bit, for example, ifthe base station determines that at least one active BWP of the cell isnot allowed to be switched by the DCI. At step 3410, the base stationmay transmit, for example, DCI with an action indication fieldconfigured with one bit that indicates actions to be performed by thewireless device (e.g., as described above with reference to FIG. 28B,FIG. 29B, or FIG. 30B).

FIG. 35 shows an example of configuring a plurality of BWPs. A basestation 3502 may transmit one or more messages, comprising configurationparameters 3512 of a cell, to a wireless device 3504. The configurationparameters may correspond to one or more RRC messages (e.g., one or moreof an RRC connection configured message, an RRC connectionreestablishment messages, and an RRC connection setup message, etc.).The configuration parameters 3512 may comprise a configuration of aplurality of BWPs 3506 of the cell. The plurality of BWPs may compriseN+1 BWPs: BWP 0, BWP 1, BWP 2 . . . BWP N. The wireless device 3504 mayreceive the one or more messages at time t₀.

The wireless device 3504 may activate, for example, a first BWP (e.g.,an initial BWP, a default BWP, etc.) at t₁. The wireless device 3504 mayactivate additional BWP(s) of the plurality of BWPs 3506 at t₁. Thewireless device 3504 may receive a MAC CE 3513 indicatingactivation/deactivation (e.g., activation or deactivation) of aplurality of BWPs at t₂. The BWP 2, the BWP 4, and the BWP 5 may beactivated, for example, based on the MAC CE 3513. The MAC CE 3513 mayalso indicate deactivation of one or more BWPs activated at or beforet₂. A single MAC CE may indicate activation/deactivation (e.g.,activation or deactivation) state changes of a plurality of BWPs at thesame time.

The base station 3502 may transmit DCI 3514 via a downlink channel, suchas a PDCCH, to indicate activation/deactivation (e.g., for reducinglatency that may be caused by the MAC CE signaling). The DCI 3514 may betransmitted via the first BWP (e.g., a primary BWP). The first BWP maybe unswitchable by DCI (e.g., but may be switchable by an RRC message).The DCI 3514 may comprise, for example, a BWP ID field. The BWP ID fieldmay indicate a BWP state (activation/deactivation) toggling of a BWP asindicated in the BWP ID field. The DCI 3514 may not comprise an actionindication field (or an action indication field may be used for anotherpurpose). The wireless device 3504 may receive the DCI 3514 at time t₃.The wireless device 3504 may determine that the DCI 3514 indicatesdeactivating the active BWP 2 to an inactive state (e.g., toggling fromactive to inactive), for example, if the BWP ID field indicates theactive BWP 2. The wireless device 3504 may determine that the DCI 3514indicates deactivating the active BWP 2 to an inactive state (e.g.,toggling from active to inactive), for example, if the BWP ID fieldindicates the active BWP 2 and one or more DCI fields of the DCI are setto predefined values. The wireless device 3504 may determine that theDCI 3514 indicates activating an inactive BWP 3 to an active state(e.g., toggling from inactive to active), for example, if the BWP IDfield indicates the active BWP 3.

The base station 3502 may transmit DCI 3514 via a downlink channel, suchas a PDCCH, to indicate switching (e.g., for reducing latency that maybe caused by the MAC CE signaling). The DCI 3514 may be transmitted viaan active BWP (e.g., the BWP 2 other than the unswitchable primary BWP).The DCI 3514 may comprise, for example, a BWP ID field. The BWP ID fieldmay indicate a switching of the active BWP (e.g., the BWP 2) to adifferent BWP (e.g., an inactive BWP 3) as indicated in the BWP IDfield. The DCI 3514 may not comprise an action indication field (or anaction indication field may be used for another purpose). The wirelessdevice 3504 may receive the DCI 3514 at time t₃.

The wireless device 3204 may determine, for example, one of: anactivation, a deactivation, or a switch to a BWP, indicated by the BWPID field, at time t₄. The activation and the deactivation may be basedon the primary BWP. The switching may be based on the active BWP viawhich the DCI is transmitted 3514. One or more DCIs and/or one or moreMAC CEs may be transmitted between t₁ and t₂ and/or between t₂ and t₃,etc.

FIG. 36 shows an example of a procedure at a cell that may be configuredwith a plurality of BWPs. A base station 3602 may transmit one or moremessages, comprising configuration parameters 3612 of a cell, to awireless device 3604. The configuration parameters may correspond to oneor more RRC messages (e.g., one or more of an RRC connection configuredmessage, an RRC connection reestablishment messages, and an RRCconnection setup message, etc.). The configuration parameters 3612 maycomprise a configuration of a plurality of BWPs 3606 of the cell. Theplurality of BWPs may comprise N+1 BWPs: BWP 0, BWP 1, BWP 2 . . . BWPN. The wireless device 3604 may receive the one or more messages at timet₀.

The wireless device 3604 may activate, for example, a first BWP (e.g.,an initial BWP, a default BWP, etc.) at t₁. The wireless device 3604 mayactivate additional BWP(s) of the plurality of BWPs 3606 at t₁. Thewireless device 3604 may receive a MAC CE 3613 indicatingactivation/deactivation (e.g., activation or deactivation) of aplurality of BWPs at t₂. The BWP 2, the BWP 4, and the BWP 5 may beactivated, for example, based on the MAC CE 3613. The MAC CE 3613 mayindicate deactivation of one or more BWPs activated at or before t₂. Asingle MAC CE may indicate activation/deactivation (e.g., activation ordeactivation) state changes of a plurality of BWPs at the same time.

The base station 3602 may transmit DCI 3614 via a downlink channel, suchas a PDCCH. The DCI 3614 may be transmitted via the first BWP (e.g., aprimary BWP). The DCI 3614 may comprise, for example, a BWP ID field andan action indication field. The action indication field may indicate,based on its contents, one of: a switching of a BWP as indicated in theBWP ID field or an activation/deactivation toggling of a BWP asindicated in the BWP ID field. The action indication field may be, forexample, one bit in length (or any quantity of bits in length). Thewireless device 3604 may receive the DCI at time t₃. The wireless device3604 may interpret the contents of the action indication field in theDCI based on a predefined rule, for example, such as per the table 3608.The wireless device 3204 may interpret the contents of the actionindication field based on the predefined rule, such as per the table3608, for example, if the BWP ID field indicates a BWP different fromthe first BWP.

The BWP ID field may indicate, for example, a BWP ID corresponding tothe second BWP. The wireless device 3604 may determine, for example, oneof: an activation of the second BWP, a deactivation of the second BWP,and a switch to the second BWP, based on the contents of the actionindication field, at time t₄. The wireless device 3604 may switchoperation to the second BWP, for example, by deactivating the first BWPand activating the second BWP, for example, if contents of the actionindication field indicate a first value (e.g., “1”). The wireless device3604 may activate the second BWP, for example, if contents of the actionindication field indicate a second value (e.g., “0”) and the second BWPis in inactive state. The wireless device 3604 may deactivate the secondBWP, for example, if contents of the action indication field indicatethe second value (e.g., “0”) and the second BWP is in active state. Thewireless device 3604 may perform UL/DL operations on active BWPs sdetermined at time t₄.

FIG. 37 shows an example method of configuring a plurality of BWPs. Theprocedure of FIG. 37 may correspond to operations of a base stationassociated with the cell. At step 3702, the base station may determineone or more BWP changes associated with a wireless device. At step 3704,the base station may determine urgency (e.g., based on a type ofservice, such as eMBB, URLLC, etc.) and/or amount of BWP changes (e.g.,a quantity of BWP changes such as activation, deactivation, switching,etc.). At step 3705, the base station may determine one or more BWPchanges are urgent and/or the amounts of BWP changes satisfy a threshold(e.g., the amounts are less than the threshold). The base station maydetermine, for example, that a BWP switching from a BWP 1 to a BWP 2 isurgent and that BWP activation/deactivation (e.g., activation ordeactivation) of BWPs 3, 4, 5, 6, and 7 are not urgent. At step 3706,the base station may determine one or more DCIs for a first BWP change,for example, if the first BWP change is urgent and/or its amounts aresatisfying a threshold (e.g., the number of BWPs to be changed is lessthan the threshold). The base station may determine DCI for theswitching of BWP 1 to the BWP 2.

At step 3707, the base station may determine one or more BWP changes arenot urgent and/or the amounts of BWP changes do not satisfy a threshold(e.g., the quantity of BWP changes is greater than the threshold). Thebase station may determine, for example, that a BWP switching from a BWP1 to a BWP 2 is urgent and that BWP activation/deactivation (e.g.,activation or deactivation) of BWPs 3, 4, 5, 6, and 7 are not urgent. Atstep 3708, the base station may determine a MAC CE for a second BWPchange, for example, if the second BWP change is not urgent and/or itsamounts are not satisfying a threshold (e.g., the number of BWPs to bechanged is greater than the threshold). The base station may determine aMAC CE for the activation/deactivation of the BWPs 3, 4, 5, 6, and 7.

A problem may arise, for example, if multiple active BWPs are supported,for managing a BWP actions (e.g., activation, deactivation, switching,etc.), such as by using an inactivity timer. A BWP switching and/ordeactivation operation may be performed, for example, based on one ormore BWP inactivity timers expiring. A first active BWP may schedule asecond BWP and, based on a time period of inactivity, a wireless devicemay switch to a default BWP. The wireless device may have difficulty indetermining from which BWP the wireless device shall switch to thedefault BWP. The wireless device may have difficulty in determining astate of the second BWP scheduled by the first BWP, based on the firstBWP switching. Misalignment between a base station and a wireless devicemay occur based on a state of one or more active BWPs. The wirelessdevice may deactivate a second active BWP of the cell, for example,based on switching a first active BWP of a cell to a default BWP. Thewireless device may restart a BWP inactivity timer for a first activeBWP of the cell, for example, based on DCI being sent via the firstactive BWP and/or based on receiving DCI activating, deactivating,and/or switching a second BWP of a cell.

A wireless device may have difficulty determining a state of a secondBWP based on switching of a first BWP to a default BWP, for example, ifmultiple active BWPs are supported. The wireless device may havedifficulty determining from which BWP the wireless device shall switchto the default BWP, and/or determining a state of the second BWP, forexample, based on the second BWP being scheduled by the first BWP and/orthe first BWP switching to another BWP. Misalignment between a basestation and the wireless device may occur regarding a state of one ormore active BWPs. The first BWP and second BWP may have a similar orsame numerology. The default BWP numerology may be different from thefirst BWP and/or second BWP. The difference in numerology between BWPsmay cause difficulty for the wireless device (e.g., misalignment, linkinterruption, power drain, synchronization, etc.). The wireless devicemay miss detecting a further instruction from the base station via thefirst BWP, based on the first BWP having switched to a default BWP.

A wireless device may deactivate a second BWP based on a first BWPswitching to a default BWP. The wireless device may activate a first BWPbased on first DCI received from a base station (e.g., from any of oneor more base stations). The wireless device may activate a second BWPbased on second DCI, for example, after activating the first BWP. Thefirst BWP may be switched to a default BWP, for example, based on anexpiration of a time period of inactivity and/or third DCI. The secondBWP may be deactivated, for example, based on the first BWP switching tothe default BWP. This deactivating of the second BWP, based on the firstBWP switching, may reduce device power demand, reduce power consumption,simplify a wireless device's implementation, and/or reduce wirelessdevice cost. The solution may also improve system throughput, forexample, by allowing the base station to use resources of the secondactive BWP for data transmission for other wireless devices.

A wireless device may receive, via a first active BWP of a cell, DCIactivating/deactivating (e.g., activating or deactivating) a second BWPof the cell, for example, if multiple active BWPs are supported. Awireless device may miss detecting further instruction (e.g., associatedwith the second BWP) from the base station on the first active BWP, forexample, based on the first active BWP switching if a BWP timer expires.Misalignment may occur, for example, as a result of the wireless devicemissing a detection of an instruction from the base station.

A wireless device may restart a BWP inactivity timer for a first BWPbased on receiving DCI activating, deactivating, and/or switching asecond BWP. The wireless device may activate a first BWP based on firstDCI received from a base station. The wireless device may activateand/or deactivate a second BWP based on second DCI, for example, afteractivating the first BWP. The BWP inactivity timer for the first BWP maybe reset, for example, based on the second DCI. This reset of the BWPinactivity timer may reduce unexpected BWP switching to a default BWP.For example, if a wireless device is configured to switch to a defaultBWP based on a period of inactivity (e.g., an expiration of aninactivity timer), the wireless device may prevent such BWP switching byresetting the BWP inactivity timer prior to reaching the end of athreshold period of inactivity (e.g., an expiration of an inactivitytimer). This reset of the BWP inactivity timer may improve systemthroughput and/or reduce signaling overhead which otherwise may be usedto maintain the active state of the first active BWP. The wirelessdevice may reduce the frequency of missing an instruction from the basestation via the first BWP, based on the first BWP having switched to adefault BWP.

Deactivating a second BWP (e.g., based on a first BWP switching to adefault BWP), and/or restarting a BWP inactivity timer for a first BWP(e.g., based on receiving DCI activating and/or deactivating a secondBWP) may provide an efficient BWP operation mechanism for supportingmultiple active BWPs operation in a cell. Deactivating a second BWP,and/or restarting a BWP inactivity timer, may provide increasedefficiency of BWP management for supporting multiple active BWPsoperations in a cell.

A base station may send one or more messages comprising configurationparameters of a plurality of cells. At least one cell of the pluralityof cells may comprise a plurality of BWPs comprising a default BWP. Theconfiguration parameters may indicate that the at least one cell may beassociated with a BWP timer and a timer value. A first timer valueassociated with a first cell of the at least one cell may be the same asor different from a second timer value associated with a second cell ofthe at least one cell.

A base station may send, to a wireless device, a PDCCH of a first activeBWP. The wireless device may start a BWP timer (e.g., a BWP inactivitytimer) using a timer value based on receiving the PDCCH via the firstactive BWP.

A base station may send first DCI via a PDCCH on or using a first activeBWP of a first cell, of the at least one cell, for scheduling a secondBWP of a second active cell of the at least one cell, for example, ifcross-carrier scheduling is supported. The wireless device maytransition the second BWP of the second cell from an inactive state toan active state, for example, if the second BWP is in an inactive statebefore receiving the first DCI. The wireless device may start and/orrestart a first BWP timer with a timer value associated with the firstcell (or the first active BWP), for example, based on receiving thefirst DCI. The wireless device may start and/or restart a second BWPtimer with the timer value associated with the second cell (or thesecond BWP), for example, based on receiving the first DCI via the firstactive BWP. The base station and/or the wireless device may switch tothe default BWP as an active BWP, based on an expiry of the BWP timerassociated with the at least one cell.

Some BWP and/or CA operations (e.g., by legacy devices and/or other byother devices) may allow at most one active BWP in a cell. The cell maybe associated with a BWP timer and/or a timer value. A wireless devicemay start the BWP timer using the timer value, for example, based on orin response to receiving first DCI via a first BWP (e.g., an activeBWP). The wireless device may switch to a second BWP, for example, basedon or in response to receiving the first DCI for BWP switching from thefirst BWP to the second BWP. The wireless device may start and/orrestart the BWP timer with the timer value, for example, based on or inresponse to the BWP switching. Some BWP operations (e.g., by legacydevices and/or by other devices) may not support multiple active BWPs ina cell. Some BWP and/or CA operations (e.g., by legacy devices and/or byother devices) may not efficiently manage a state (e.g., active stateand/or inactive state) of multiple active BWPs, for example, if multipleactive BWPs are supported. Some BWP and/or CA operations (e.g., bylegacy devices and/or other devices) may not efficiently manage a state(e.g., active state or inactive state) of multiple active BWPs, forexample, if multiple active BWPs are supported, and/or if multiple BWPtimers are associated with the multiple active BWPs.

A base station and/or a wireless device may communicate via multipleactive BWPs of a plurality of BWPs for sending and/or receiving multipletypes of services in a cell. Each of the plurality of BWPs may be in anactive state or an inactive state. The plurality of BWPs may comprise adefault BWP. The default BWP may be in an inactive state, for example,if the default BWP is different from one or more of the multiple activeBWPs. A wireless device may switch a first active BWP of the multipleactive BWPs to the default BWP, for example, based on or in response toat least one of: receiving DCI indicating BWP switching to the defaultBWP, and/or a first BWP timer associated with the first active BWPexpiring. A wireless device may switch a second active BWP of themultiple active BWPs to the default BWP, for example, based on or inresponse to at least one of: receiving DCI indicating BWP switching tothe default BWP, and/or a second BWP timer associated with the secondactive BWP expiring. The first inactivity timer may be associated with afirst timer value. The second inactivity timer may be associated with asecond timer value.

A base station may send one or more messages comprising configurationparameters indicating a default BWP and/or a plurality of BWPs in acell. The configuration parameters may indicate each of the plurality ofBWPs may be associated with a BWP specific timer that may differ fromother BWPs, and/or a BWP timer value that may differ from other BWPs. Afirst BWP timer value of a first BWP of the plurality of BWPs may bedifferent from a second BWP timer value of a second BWP of the pluralityof BWPs. The configuration parameters may indicate each of the pluralityof BWPs may be associated with a particular BWP timer and/or a celltimer value. The BWP timers of the plurality of BWPs may be associatedwith the same cell timer value.

A base station may send one or more messages comprising configurationparameters indicating a cell comprising a default BWP and/or a pluralityof BWP groups. The configuration parameters may indicate each BWP groupof the plurality of BWP groups are associated with a BWP group specifictimer and/or a BWP group timer value.

FIG. 38 shows an example of BWP management comprising BWP deactivationof a secondary BWP in a cell. A wireless device 3802 may be configuredfor at least two active BWPs, such as a primary BWP 3804 (e.g., BWP 0)and a secondary BWP 3808 (e.g., BWP 1). The wireless device 3802 mayreceive one or more messages to activate one or more BWPs, for exampleat an initial time 3810 (e.g., T0). The wireless device 3802 may receiveone or more transport blocks (TBs) via the active BWPs (e.g., BWP 0and/or BWP 1), for example, after the initial time 3810 (e.g., T0). Thewireless device 3802 may be configured with at least one inactive BWP,such as a default BWP 3806 (e.g., BWP 2). At a first time period 3812(e.g., T1), the wireless device 3802 may switch from the primary BWP3804 to the default BWP 3806, for example, based on or in response to aperiod of inactivity (e.g., a timer expiration) and/or receiving DCI(e.g., indicating switching). After the first time period 3812, theprimary BWP 3802 may be inactive and the default BWP 3806 may be active.The wireless device 3802 may switch from a primary BWP to a secondaryBWP, for example, based on a timer and/or DCI. The wireless device 3802may activate the default BWP (e.g., BWP 2) and/or deactivate BWP 1, forexample, based on BWP switching. At or after the first time period 3812(e.g., T1), the wireless device 3802 may deactivate the secondary BWP3808 (e.g., BWP 1) of the cell, for example, based on switching theprimary BWP 3804 to the default BWP 3806. The switching may be based ona timer (e.g., expiration of a BWP inactivity timer) and/or based onreceiving DCI (e.g., indicating BWP 2). The secondary BWP 3808 (e.g.,BWP 1) may be scheduled by the primary BWP 3804, for example, byconfiguring PDCCH for the secondary BWP 3808 on the primary BWP 3804.The secondary BWP 3808 may be configured with a wireless device specificsearch space. The primary BWP 3804 may be configured with a commonsearch space. The secondary BWP 3808 may be configured to have a samenumerology as the primary BWP 3804, which may reduce signal receivingimplementation complexity. Reducing signal receiving complexity may beadvantageous for various applications, such as vehicle-to-anything(V2X), URLLC, and/or any other application (e.g., service type). Theprimary BWP 3804 (e.g., BWP 0, a Uu BWP, etc.) may have a samenumerology as a secondary BWP (e.g., BWP 1, a sidelink BWP, etc.).

FIG. 39 shows an example of BWP management using multiple active BWPs ina cell. A wireless device 3902 may start a first BWP timer (e.g., a BWPinactivity timer) at an initial time 3910 (e.g., T0). The wirelessdevice 3902 may restart the first BWP timer (e.g., a BWP inactivitytimer) for a primary BWP 3904 (e.g., BWP1) of a cell, for example, basedon receiving DCI at a first time 3912 (e.g., T1) activating,deactivating, and/or switching a second BWP 3906 (e.g., BWP2) of thecell. By restarting the first BWP timer at the first time 3912, thewireless device may prevent from switching to a default BWP (not shown)that may otherwise result if the timer expires (e.g., if the timer is aBWP inactivity timer). The second BWP 3906 (e.g., BWP2) may not beaccessible to the wireless device 3902, for example, based on switchingto the default BWP. A base station may send the DCI on or using theprimary BWP 3904 (e.g., BWP1). The default BWP (not shown) may beconfigured with a narrow bandwidth, for example, which may notaccommodate cross-BWP scheduling of the second BWP 3906. The wirelessdevice 3902 may activate or deactivate the second BWP 3906 (e.g., BWP2),based on receiving DCI on or using the primary BWP 3904 (e.g., BWP1) toactivate or deactivate, respectively, the second BWP (e.g., BWP2). Forexample, the wireless device 3902 may receive, on or using the primaryBWP 3904, DCI at a first time period 3912 (e.g., T1). The DCI mayindicate activation or deactivation of the secondary BWP 3906. Thewireless device 3902 may activate or deactivate the second BWP 3906, forexample, based on the DCI (e.g., at or after the first time period3912). Cross-BWP activation/deactivation (e.g., activation ordeactivation) may improve communications between a base station and thewireless device 3902, such as by reducing misalignment, reducing powerconsumption, and/or reducing signaling overhead.

FIG. 40 shows an example of BWP management with multiple BWPs in a cell.A wireless device 4002 may start and/or restart BWP timers based on BWPactivation and/or receipt of DCI. The wireless device 4002 may startand/or restart a first BWP timer at an initial time 4010 (e.g., T0), forexample, based on or in response to activating a first BWP 4004 (e.g.,BWP 0). The wireless device 4002 may start and/or restart a second BWPtimer at a first time 4012 (e.g., T1), for example, based on activatinga second BWP 4006 (e.g., BWP 1). The wireless device 4002 may receivefirst DCI via a first PDCCH at a second time 4014 (e.g., T2) via thefirst BWP 4004 of the multiple BWPs. The wireless device 4002 may startand/or restart a first BWP specific timer associated with a first BWP4004 (or a cell) using a first timer value, for example, based onreceiving the first DCI via the first BWP 4004. The wireless device 4002may receive second DCI at a third time 4016 (e.g., T3) via a secondPDCCH on or using the second BWP 4006 of the multiple BWPs. The wirelessdevice 4002 may start and/or restart a second BWP timer associated witha second BWP (or the cell) using a second timer value, for example,based on receiving the second DCI via the second BWP 4006. The wirelessdevice 4002 may independently manage the first BWP timer associated withthe first BWP 4004 and/or the second BWP timer associated with thesecond BWP 4006.

The wireless device 4002 may start and/or restart a first BWP groupspecific timer using a first BWP group (or a cell) timer value, forexample, based on receiving DCI on or using a first BWP of a first BWPgroup of a plurality of BWP groups. The wireless device may start and/orrestart a second BWP group specific timer using a second BWP group (orthe cell) timer value, for example, based on receiving DCI on or using asecond BWP of a second BWP group of the plurality of BWP groups. Thewireless device may independently manage the first BWP group specifictimer of the first BWP group and the second BWP group specific timer ofthe second BWP group.

FIG. 41 shows an example of BWP management with a primary BWP andmultiple secondary BWPs in a cell. A wireless device 4102 may startand/or restart one or more BWP timers, for example, based on receivingone or more DCIs, and/or based on switching between a first secondaryBWP 4106 and a second secondary BWP 4108. A wireless device 4102 mayconfigure a primary BWP 4104 (e.g., BWP 0) for use, for example, at orbefore an initial time 4110 (e.g., T0). The wireless device 4102 maystart and/or restart a first BWP timer at a first time 4112 (e.g., T1),for example, based on or in response to activating a first secondary BWP4106 (e.g., BWP1). The wireless device 4102 may start and/or restart asecond BWP timer at a second time 4114 (e.g., T2), for example, based onor in response to activating and/or switching to a second secondary BWP4108 (e.g., BWP2). The wireless device 4102 may restart and/or start afirst BWP timer at third time 4116 (e.g., T3), for example, based on orin response to receiving DCI on or using the first secondary BWP 4106.The wireless device 4102 may restart and/or start a second BWP timer attime T4 4118, for example, based on receiving DCI via the secondsecondary BWP 4108. By starting/restarting a timer (e.g., the first BWPtimer, the second BWP timer, etc.), the wireless device 4102 may preventfrom switching to a default BWP (not shown) that may otherwise result ifthe timer expires (e.g., if the timer is a BWP inactivity timer).

A base station may send, to the wireless device 4102, one or moremessages comprising configuration parameters indicating a cellcomprising a primary active BWP and multiple secondary BWPs in a cell.The configuration parameters may indicate each of the plurality of BWPsbe associated with a BWP specific timer, a BWP timer value, and/or acell specific timer value. A primary active BWP (e.g., primary BWP 4104)may remain in an active state until receiving a second commandindicating a primary active BWP switching. The second command maycomprise an RRC message, a MAC CE, and/or DCI (e.g., DCI indicating aprimary active BWP switching). The primary active BWP may not beassociated with a BWP specific timer. The wireless device 4102 maymanage a first BWP specific timer of a first BWP of multiple BWPs, and asecond BWP specific timer of a second BWP of the multiple BWPsindependently. The wireless device 4102 may keep the primary active BWPactive until receiving the second command

FIG. 42 shows an example of BWP management using cross-BWP schedulingfor multiple active BWPs in a cell. A wireless device 4202 may startand/or restart one or more BWP timers based on BWP activation and/orreceiving DCI. The wireless device 4202 may start and/or restart a firstBWP timer at an initial time 4210 (e.g., T0), for example, based on orin response to activation of a first BWP 4202 (e.g., BWP0). The wirelessdevice 4202 may start and/or restart a second BWP timer at first time4212 (e.g., T1), for example, based on or in response to activation of asecond BWP 4206. The wireless device 4202 may receive first DCI via thefirst BWP 4204 indicating cross-scheduling (e.g., cross-BWP scheduling)on the second BWP 4206. The wireless device 4202 may restart and/orstart the first BWP timer and/or the second BWP timer at a second time4214 (e.g., T2), for example, based on receiving the first DCI. Forexample, the wireless device 4202 may start and/or restart the secondBWP timer associated with the second BWP 4206 based on or in response toreceiving an indication of activation of the first BWP 4204 and/or DCIon or using the first BWP 4204. By activating the second BWP 4206,starting the second BWP timer, and/or restarting the second BWP timer inthe above manner, the wireless device 4202 may improve communicationswith a base station, such as by reducing misalignment, reducing powerconsumption, and/or reducing signaling overhead.

A base station may send first DCI via a first BWP (e.g., a first DL BWP)of a plurality of BWPs. The first DCI may indicate a DL assignment or anUL grant for a second BWP of the plurality of BWPs. The first BWP may beassociated with a first BWP specific timer and/or a first BWP timervalue (or a cell timer value). The first BWP may be a primary activeBWP. The second BWP may be associated with a second BWP specific timerand/or a second BWP timer value (or a cell timer value). The wirelessdevice may start and/or restart the first BWP specific timer using thefirst BWP timer value (or the cell timer value), for example, based onor in response to receiving the first DCI. The wireless device may startand/or restart the second BWP specific timer using the second BWP timervalue (or the cell timer value), for example, based on or in response toreceiving the first DCI.

First DCI sent via a first BWP may indicate a configured (or dynamic)downlink assignment via a second BWP (e.g., a second DL BWP). The firstDCI sent via the first BWP may indicate a configured (or dynamic) uplinkgrant via the second BWP (e.g., an UL BWP). The first DCI sent via thefirst BWP may be sent via a PDCCH addressed to a first identifier viathe first BWP. The first identifier may be at least one of C-RNTI and/orCS-RNTI. The first identifier may be at least one of: SI-RNTI, RA-RNTI,TC-RNTI, P-RNTI, INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI,TPC-SRS-RNTI, CS-RNTI, SP-CSI-RNTI, and/or C-RNTI.

FIG. 43 shows an example of BWP management using cross-BWP schedulingfor multiple active BWPs in a cell. A wireless device 4302 may performcross-BWP scheduling, for example, by activating a second BWP 4306(and/or start and/or restart a second BWP timer) based on or in responseto receiving DCI via a first BWP 4304 (e.g., BWP0) indicating activatingthe second BWP 4306 (e.g., BWP1). A wireless device 4302 may receive(e.g., from a base station) an indication of a BWP activation for thefirst BWP 4304, for example, at an initial time 4310 (e.g., T0). Thewireless device 4302 may start and/or restart a first BWP timer, forexample, based on or in response to the indication of the BWP activationfor the first BWP 4304. The base station may send second DCI (and/or aMAC CE) on or using the first BWP 4304 indicating activating the secondBWP 4306. The first BWP 4304 may be associated with a first BWP specifictimer and/or a first BWP timer value (or a cell timer value). The firstBWP 4304 may be a primary active BWP. The second BWP 4306 may beassociated with a second BWP specific timer and/or a second BWP timervalue (or a cell timer value). The wireless device 4302 may start and/orrestart the first BWP specific timer using the first BWP timer value (orthe cell timer value) at a first time 4312 (e.g., T1), for example,based on or in response to receiving the second DCI. The wireless device4302 may activate the second BWP 4306, for example, based on or inresponse to receiving the second DCI. The wireless device may startand/or restart the second BWP specific timer using the second BWP timervalue (or the cell timer value) at a second time 4314 (e.g., T2), forexample, based on the activating the second BWP 4306. A gap may be zeroor a value greater than zero, between the first time 4312 (e.g., a firsttime after DCI for the activation is received) and the second time 4314(e.g., a second time after the activation is complete).

A base station may send third DCI (and/or a MAC CE) on or using a firstBWP of a plurality of BWPs. The third DCI may indicate deactivating asecond BWP of the plurality of BWPs. The first BWP may be associatedwith a first BWP specific timer and/or a first BWP timer value (or acell timer value). The first BWP may be a primary active BWP. The secondBWP may be associated with a second BWP specific timer and/or a secondBWP timer value (or a cell timer value). The wireless device may notstart and/or restart the first BWP specific timer using the first BWPtimer value (or the cell timer value), for example, based on or inresponse to receiving the second DCI. The wireless device may deactivatethe second BWP, for example, based on or in response to receiving thesecond DCI. The wireless device may reset the second BWP specific timerto the second BWP specific timer value (or the cell specific timervalue) and/or not start the second BWP specific timer, for example,based on or in response to the deactivating the second BWP.

FIG. 44 shows an example of BWP management for multiple active BWPs in acell. A wireless device 4402 may activate a BWP, deactivate a BWP, starta BWP timer, and/or restart BWP timers based on switching BWPs. Awireless device 4402 may receive an indication for activating a firstBWP 4404 (e.g., BWP0), for example, at an initial time 4410 (e.g., T0).The wireless device 4402 may start and/or restart a first BWP timer atthe initial time 4410, for example, based on activation of the first BWP4404. A base station may send fourth DCI on or using the first activeBWP 4404 indicating switching from a second active BWP 4406 to a thirdBWP 4408 as a third (or additional) active BWP. The first BWP 4404 maybe associated with a first BWP specific timer and/or a first BWP timervalue (or a cell timer value). The first BWP 4404 may be a primaryactive BWP. The second BWP 4406 may be associated with a second BWPspecific timer and/or a second BWP timer value (or a cell timer value).The third BWP 4408 may be associated with a third BWP specific timerand/or a third BWP timer value (or a cell timer value). The wirelessdevice 4402 may start and/or restart the first BWP specific timer usingthe first BWP timer value (or the cell timer value) at a first time 4412(e.g., T1), for example, based on or in response to receiving the fourthDCI. The wireless device 4402 may deactivate the second active BWP 4406and/or activate the third BWP 4408 as the third active BWP, for example,based on or in response to receiving the fourth DCI. The wireless device4402 may reset the second BWP specific timer using the second BWP timervalue (or the cell timer value) and/or not start the second BWP specifictimer at the first time 4412, for example, based on or in response tothe deactivating the second active BWP. The wireless device 4402 maystart and/or restart the third BWP specific timer using the third BWPtimer value at a second time 4414 (e.g., T2) (or the cell timer value),for example, based on or in response to the activating the third BWP. Agap may be zero or a value greater than zero, between the first time4412 (e.g., a first time after DCI for the switching is received) andthe second time 4414 (e.g., a second time after the switching iscompleted). By switching from the second BWP 4406 to the third BWP 4408based on or in response to DCI on or using the first BWP 4404, thewireless device 4402 may improve communications with a base station,such as by reducing misalignment, reducing power consumption, and/orreducing signaling overhead.

A base station may send one or more messages comprising configurationparameters indicating a cell comprising a default BWP and a plurality ofBWPs in a cell. The configuration parameters may indicate each of theplurality of BWPs may be associated with a BWP specific timer and/or aBWP timer value or a cell timer value. A first active BWP of multipleactive BWPs of the plurality of BWPs may be designated as a primaryactive BWP (PBWP). At least a second active BWP of multiple active BWPsof the plurality of BWPs may be designated as a secondary active BWP(SBWP). The default BWP may be in an inactive state if the default BWPis different from the PBWP.

A wireless device may start and/or restart a first BWP specific timer,for example, based on or in response to receiving a first commandindicating at least one of: the PBWP being activated, a PBWP switching,and/or DL assignment/UL grant on or using the PBWP. The wireless devicemay start and/or restart a second BWP specific timer, for example, basedon or in response to receiving a second command indicating at least oneof: the SBWP being activated, a SBWP switching, and/or DL assignment/ULgrant on or using the SBWP.

The wireless device may monitor a first PDCCH on or using the PBWP, forexample, if the first BWP specific timer is running. The wireless devicemay monitor a second PDCCH on or using the SBWP, for example, if thesecond BWP specific timer is running

The wireless device may deactivate the SBWP, for example, based on or inresponse to the second BWP specific timer expiring and the first BWPspecific timer running. The wireless device may keep the PBWP in anactive state, for example, based on or in response to the second BWPspecific timer expiring and the first BWP specific timer running. Thewireless device may keep the default BWP in an inactive state, forexample, based on or in response to the second BWP specific timerexpiring and the first BWP specific timer running

FIG. 45 shows an example of BWP management using a primary BWP, adefault BWP, and at least a secondary BWP in a cell. A wireless device4502 may not switch to a default BWP (e.g., BWP2) until at least anexpiration of multiple (or all) BWP timers associated with multiple (orall) active BWPs. By not switching to a default BWP at or after anexpiration of a first BWP timer (e.g., at T2), the wireless device 4502may improve communications with a base station, such as by reducingmisalignment, reducing power consumption, and/or reducing signalingoverhead. The wireless device 4502 may activate a first BWP, such as aprimary BWP 4504 (e.g., BWP0), for example, based on or in response toreceiving an indication for activation of the first BWP at an initialtime 4510 (e.g., T0). The wireless device 4502 may start a first BWPtimer based on or in response to the primary BWP 4504 activation. Thewireless device 4502 may activate a second BWP, such as a secondary BWP4508 (e.g., BWP0), for example, based on or in response to receiving anindication for activation of the second BWP at a first time 4512 (e.g.,T1). The wireless device 4502 may start a second BWP timer based on orin response to the secondary BWP 4508 activation. The wireless device4502 may switch and/or deactivate BWPs based on a greater of multipleBWP timers expiring. For example, if the first BWP timer is stillrunning, the wireless device 4502 may not switch from the secondary BWP4508 to the default BWP 4506, based on or in response to the second BWPtimer expiring (e.g., at a second time 4512). If the greater of the BWPtimers associated with active BWPs expires (e.g., at a third time 4516),the wireless device 4502 may switch from the primary BWP 4504 to thedefault BWP 4506 at fourth time 4518 (e.g., T4), for example, based onthe second BWP timer expiring and the first BWP timer both havingexpired. The wireless device 4502 may switch from the primary BWP 4504to the default BWP 4506, for example, based on one or more BWP timersexpiring (e.g., the last of a plurality of BWP timers each associatedwith an active BWP). The one or more BWP timers may comprise at leastthe second BWP timer and the first BWP timer. The wireless device 4502may activate the default BWP 4506 and deactivate the primary BWP 4504,for example, based on the switching. A gap may be zero or a valuegreater than zero, between the third time 4516 (e.g., a first time afterthe switching is started) and the fourth time 4518 (e.g., a second timeafter the switching is completed). The wireless device may deactivatethe secondary BWP 4508 based on or in response to the BWP switching fromthe primary BWP 4504 to the default BWP 4506. Deactivating the secondaryactive BWP 4508 in the manner described above may conserve wirelessresources, for example, relative to switching the secondary BWP 4508 tothe default BWP 4506. The secondary BWP 4508 and/or an additional BWP(not shown) may be activated, for example, based on the wireless device4502 receiving an addition indication for activation of a BWP (notshown), which may be more efficient than switching the secondary BWP4508 to a third BWP.

A base station may send one or more messages comprising configurationparameters indicating a cell comprising a default BWP and multiple otherBWPs in a cell. The configuration parameters may indicate each of theBWPs may be associated with a BWP specific timer and/or a BWP timervalue or a cell timer value. A first active BWP of multiple active BWPsmay be designated as a primary active BWP (PBWP). At least a secondactive BWP of multiple active BWPs may be designated as a secondaryactive BWP (SBWP). The default BWP may be in an inactive state, forexample, if the default BWP is different from the PBWP. The SBWP may benot configured with a PDCCH. A base station may send a downlinkscheduling and/or an uplink grant for the SBWP via a PDCCH on or usingthe PBWP. The SBWP may be not associated with a BWP specific timer, forexample, if the SBWP is not configured with a PDCCH via the SBWP.

A wireless device may start and/or restart a first BWP specific timer,for example, based on or in response to receiving a first commandindicating at least one of: the PBWP being activated, a PBWP switching,a DL assignment via the PBWP, and/or a UL grant on or using the PBWP.The wireless device may start and/or restart a second BWP specific timer(if configured), for example, based on or in response to receiving asecond command indicating at least one of: the SBWP being activated, aSBWP switching, a DL assignment via the SBWP, and/or a UL grant via theSBWP.

The wireless device may monitor a first PDCCH on or using the PBWP, forexample, if the first BWP specific timer is running. The wireless devicemay monitor the first PDCCH or a second PDCCH on or using the PBWP forthe SBWP, for example, if the second BWP specific timer is running

FIG. 46 shows an example of BWP management using a primary BWP, defaultBWP, and at least a secondary BWP in a cell. A wireless device 4602 mayswitch to a default BWP (e.g., BWP2) and/or deactivate a secondary BWP,for example, if a primary BWP timer expires. By switching to a defaultBWP at or after an expiration of a primary BWP timer (e.g., at T4), thewireless device 4602 may improve communications with a base station,such as by reducing misalignment, reducing power consumption, and/orreducing signaling overhead. The wireless device 4602 may activate afirst BWP, such as a primary BWP 4604 (e.g., BWP0), for example, basedon or in response to receiving an indication for activation of the firstBWP at an initial time 4610 (e.g., T0). The wireless device 4602 maystart a first BWP timer based on or in response to the primary BWP 4604activation. The wireless device 4602 may activate a second BWP, such asa secondary BWP 4608 (e.g., BWP0), for example, based on or in responseto receiving an indication for activation of the second BWP at a firsttime 4612 (e.g., T1). The wireless device 4602 may start a second BWPtimer based on or in response to the secondary BWP 4608 activation. Thewireless device 4602 may switch and/or deactivate BWPs based on theprimary BWP timer expiring. The wireless device 4602 may deactivate asecondary BWP 4608 (e.g., BWP1) based on or in response to switchingfrom a primary BWP 4604 to a default BWP 4606. The wireless device 4602may perform BWP switching based on an expiration of one or more BWPtimers (e.g., the primary BWP timer). The wireless device may start afirst BWP timer at an initial time 4610 (e.g., T0), for example, basedon activation of the primary BWP 4608. The wireless device 4602 maystart a second BWP timer at a first time 4612 (e.g., T1), for example,based on activation of the secondary BWP 4608. The wireless device mayswitch from the primary BWP 4604 to the default BWP 4606, for example,based on a first BWP timer expiring at a second time 4614 (e.g., T2)and/or a second BWP specific timer (if configured) running (e.g., thesecondary BWP timer running) The wireless device 4602 may deactivate theprimary BWP 4604 and activate the default BWP 4606 at a third time 4614(e.g., T3), for example, based on the BWP switching. The wireless device4602 may deactivate the secondary BWP 4608, for example, based on theBWP switching of the primary BWP 4604 to the default BWP 4606. A gap maybe zero or a value greater than zero, between the second time 4614(e.g., a first time after the switching is started) and the third time4616 (e.g., a second time after the switching is completed).

A base station may send one or more messages comprising configurationparameters indicating a cell comprising a default BWP and a plurality ofBWPs in a cell. The configuration parameters may indicate each of theplurality of BWPs may be associated with a BWP specific timer and a BWPtimer value or a cell timer value.

A wireless device may start and/or restart a first BWP specific timer,for example, based on or in response to receiving a first commandindicating at least one of: a first BWP being activated, a DL assignmentvia the first BWP, and/or a UL grant on or using the first BWP. Thewireless device may start and/or restart a second BWP specific timer (ifconfigured), for example, based on or in response to receiving a secondcommand indicating at least one of: a second BWP being activated, a DLassignment via the second BWP, and/or a UL grant via the second BWP.

The wireless device may monitor a first PDCCH on or using the first BWP,for example, if the first BWP specific timer is running. The wirelessdevice may monitor a second PDCCH on or using the second BWP, forexample, if the second BWP specific timer is running

FIG. 47 shows an example of BWP management with multiple active BWPs ina cell. A wireless device 4702 may switch to a default BWP (e.g., BWP2)from a second BWP (e.g., BWP1), for example, if a BWP timer associatedwith the second BWP expires. A first BWP (e.g., BWP0) may be deactivated(e.g., and not switched to a default BWP), for example, if a first BWPtimer expires and a second BWP has switched to a default BWP. Thewireless device 4702 may activate a first BWP 4704 (e.g., BWP0), forexample, based on or in response to receiving an indication foractivation of the first BWP at an initial time 4710 (e.g., T0). Thewireless device 4702 may start a first BWP timer based on or in responseto the first BWP 4604 activation. The wireless device 4702 may activatea second BWP 4608 (e.g., BWP0), for example, based on or in response toreceiving an indication for activation of the second BWP at a first time4712 (e.g., T1). The wireless device 4702 may start a second BWP timerbased on or in response to the second BWP 4708 activation. The wirelessdevice 4702 may switch and/or deactivate BWPs based on a BWP timerexpiring. For example, the wireless device 4702 may switch from thesecond BWP 4708 to the default BWP 4706 (e.g., at a third time 4716)based on the second BWP timer expiring at a second time 4714 (e.g., T2).The wireless device 4702 may switch from the second BWP 4708 to thedefault BWP 4706 at the second time 4714 or between the second time 4714and a third time 4716 (e.g., T3), for example, based on the second BWPtimer expiring at the second time 4714 and/or the first BWP timerrunning. The wireless device 4702 may deactivate the second BWP 4708 andactivate the default BWP 4706, for example, based on the BWP switching.The wireless device 4702 may keep the first BWP 4704 in an active state,for example, based on the switching. A gap may be zero or a valuegreater than zero, between the second time 4714 (e.g., a first timeafter the switching is started) and a third time (e.g., a second timeafter the switching is complete). The wireless device 4702 maydeactivate the first BWP 4704 and keep the default BWP 4706 in activestate, for example, based on or in response to one or more BWP specifictimers (e.g., the first BWP timer) expiring. The one or more BWPspecific timers may comprise at least: the first BWP timer and/or thesecond BWP timer.

A base station may send one or more messages comprising configurationparameters indicating a cell comprising a default BWP and multiple otherBWPs in a cell. The configuration parameters may indicate each of theBWPs being associated with a BWP specific timer and/or a BWP timer valueor a cell timer value.

A wireless device may start and/or restart a first BWP specific timer,for example, based on receiving a first command indicating at least oneof: a first BWP being activated, a DL assignment via the first BWP,and/or a UL grant on or using the first BWP. The wireless device maystart and/or restart a second BWP specific timer (if configured), forexample, based on receiving a second command indicating at least one of:a second BWP being activated, a DL assignment via the second BWP, and/ora UL grant on or using the second BWP.

The wireless device may monitor a first PDCCH on or using the first BWP,for example, if the first BWP specific timer is running. The wirelessdevice may monitor a second PDCCH on or using the second BWP, forexample, if the second BWP specific timer is running

FIG. 48 shows an example of BWP management with multiple active BWPs ina cell. FIG. 48 may comprise each feature described above regarding FIG.45, except that FIG. 48 may comprise a first BWP 4804 that may (or maynot) be a primary BWP and/or a second BWP 4808 that may (or may not) bea secondary BWP. A wireless device 4802 may not switch to a default BWP(e.g., BWP2) until at least an expiration of multiple (or all) BWPtimers associated with multiple (or all) active BWPs. The wirelessdevice 4802 may cause a first BWP 4804 to switch to a default BWP 4806based on a first BWP timer expiring, for example, after a second BWP4808 is deactivated based on a second BWP timer expiring. The wirelessdevice 4802 may start a first BWP timer at an initial time 4810 (e.g.,T0), for example, based on activation of the first BWP 4804. Thewireless device 4802 may start a second BWP timer at a first time 4812(e.g., T1), for example, based on activation of the second BWP 4808. Thewireless device 4802 may deactivate the second BWP 4808, for example,based on or in response to the second BWP specific timer expiring at asecond time 4814 (e.g., T2) and/or the first BWP specific timer runningThe wireless device 4802 may deactivate the second BWP 4808, forexample, based on the BWP switching. The wireless device 4802 may keepthe first BWP 4804 in an active state, for example, based on the BWPswitching. A gap may be zero or a value greater than zero, between athird time 4816 (e.g., a first time after the switching is started) anda fourth time 4818 (e.g., a second time after the switching iscompleted).

The wireless device may switch to a default BWP, for example, based onor in response to one or more BWP specific timers expiring. The one ormore BWP specific timers may comprise at least: the first BWP specifictimer, and/or the second BWP specific timer. The wireless device maydeactivate the first BWP or the second BWP, and activate the defaultBWP, for example, based on the BWP switching.

A base station and/or a wireless device may align multiple BWP timers ifmultiple active BWPs are supported. A wireless device may reduce powerconsumption, for example, if multiple active BWPs are supported. A basestation may reduce signaling overhead to maintain time alignments and/orsynchronization on or using multiple active BWPs.

FIG. 49 shows an example method for BWP management by a wireless device.A wireless device may deactivate a first BWP, and/or monitor a PDCCH onor using the second active BWP, based on a first timer expiring and asecond timer running. At step 4902, a wireless device may receive, froma base station, one or more messages comprising RRC configuration(s)(e.g., for BWPs). At step 4904, the wireless device may activatemultiple BWPs in a cell. The wireless device may start multiple timersassociated with the multiple BWPs. At step 4906, the wireless device maymonitor a PDCCH on or using the multiple active BWPs. At step 4908, afirst timer associated with a first active BWP may expire and at least asecond timer may be running At step 4910, the wireless device maydeactivate the first active BWP, and keep at least a second active BWPin an active state. At step 4912, the wireless device may stopmonitoring a PDCCH on the first active BWP. The wireless device maymonitor at least a second PDCCH on the at least second active BWP.

A wireless device may receive, from a base station, one or more messagescomprising configuration parameters of a cell comprising a plurality ofBWPs. The plurality of BWP may comprise at least: a default BWP and afirst BWP. Each of the plurality of BWPs may be in one of an activestate and an inactive state. The wireless device may start a first BWPtimer associated with the first BWP, for example, based on or inresponse to activating the first BWP. The default BWP may be in aninactive state if the default BWP is different from the first BWP. Thewireless device may deactivate the first BWP, for example, based on orin response to the first BWP timer expiring. The wireless device mayactivate the default BWP, for example, based on each of the plurality ofBWP being in an inactive state. The wireless device may keep the defaultBWP in an inactive state, for example, based on at least a second BWPbeing in active state. The wireless device may keep the first BWP inactive state, for example, if the first BWP timer is running Thewireless device may monitor a first PDCCH on or using the first BWP, forexample, if the first BWP is in an active state.

A base station may send, to a wireless device, one or more messagescomprising configuration parameters of BWPs of a cell. The cell maycomprise a primary cell or a secondary cell. The BWPs may comprise afirst BWP and a second BWP. The configuration parameters may indicate atleast one of: a control resource set of the first BWP; a search spaceset of the first BWP; a subcarrier space of the first BWP; a number ofsymbols of the first BWP; and/or a set of resource blocks of the firstBWP. The base station and/or the wireless device may activate the firstBWP as an active BWP of the cell. The base station may send, via thefirst BWP, DCI comprising a first field and a second field. The firstfield may indicate the second BWP. Based on (or in response to) a valueof the second field and on the first field indicating the second BWP,the base station and/or the wireless device may perform: switching fromthe first BWP to the second BWP (e.g., as an active BWP); or activatingthe second BWP and maintaining active states of the first BWP and thesecond BWP. The switching from the first BWP to the second BWP maycomprise deactivating the first BWP and activating the second BWP (e.g.,as the active BWP). The switching from the first BWP to the second BWPmay comprise deactivating the first BWP during a first time durationthat is at least partially overlapped with a second time duration ofactivating the second BWP. The switching from the first BWP to thesecond BWP may comprise activating the second BWP after deactivating thefirst BWP. The deactivating the first BWP may comprise at least one of:stopping monitoring a downlink control channel on the first BWP;stopping receiving downlink signals on the first BWP; and/or stoppingtransmitting uplink signals on the first BWP. The switching from thefirst BWP to the second BWP (e.g., as the active BWP) may be performedbased on or in response to the value of the second field being set to afirst value. The activating the second BWP and maintaining the activestates of the first BWP and the second BWP may be performed based on orin response to the value of the second field being set to a secondvalue. The base station may send, to the wireless device, second DCIcomprising a third field and a fourth field. The third field mayindicate the second BWP. The base station and/or the wireless device maydeactivate, based on a value of the fourth field and on the third fieldindicating the second BWP, the second BWP. The base station and/or thewireless device may maintain, based on the value of the fourth field andon the third field indicating the second BWP, an active state of thefirst BWP. Based on the active state of the first BWP, the wirelessdevice may perform: monitoring a downlink control channel on a searchspace set (e.g., a search space set in the control resource set forreceiving a downlink radio resource assignment) associated the firstBWP; determining, based on the monitoring, a downlink radio resourceassignment; and/or receiving, based on the downlink radio resourceassignment, a downlink transport block. The wireless device may monitora downlink control channel on the search space set in the controlresource set for receiving an uplink radio resource grant; and/ortransmit, based on the uplink radio resource grant, an uplink transportblock. The wireless device may monitor a downlink control channel on thefirst BWP, receive downlink signals on the first BWP, and/or transmituplink signals on the first BWP. The second field may comprise a timeresource allocation indicator or a frequency resource allocationindicator. The second field may comprise a BWP action indicatorcomprising a value that indicates at least one of: switching an activeBWP from the first BWP to the second BWP; activating the second BWP andmaintaining the active states of the first BWP and the second BWP;and/or deactivating the second BWP and maintaining an active state ofthe first BWP. The first DCI may be received based on DCI format 1_1 orDCI format 0_1. The first DCI may be based on DCI format different fromDCI format 1_1 and from DCI format 0_1. The wireless device may monitor,on the first BWP, a downlink control channel for the first DCI. Thewireless device may activate the first BWP based on or in response toreceiving at least one of a first command indicating activation of thecell; and/or a second command indicating switching an active BWP to thefirst BWP. The first command may comprise at least one of: a radioresource control message; a MAC CE; and/or second DCI. The secondcommand may comprise at least one of: a radio resource control message;a MAC CE; and/or second DCI.

A base station and/or a wireless device may activate a first BWP of acell as a primary active BWP and a second BWP of the cell as a secondaryactive BWP. The base station may send, via the first BWP, DCI indicatinga third BWP of the cell. Based on (or in response to) the first BWPbeing the primary active BWP and based on the DCI, the base stationand/or the wireless device may maintain the first BWP as the primaryactive BWP and/or switch from the second BWP to the third BWP as thesecondary active BWP. The base station may send, to the wireless device,one or more messages comprising configuration parameters of BWPs of thecell. The BWPs may comprise the first BWP and the second BWP. Theswitching from the second BWP to the third BWP may be further based on avalue of a field of the DCI. The base station may send, via the firstBWP, second DCI comprising a first field and a second field. The firstfield may indicate the third BWP, and the second field may indicate afirst value. Based on first field indicating the third BWP and on thesecond field indicating the first value, the base station and/or thewireless device may maintain the first BWP as an active BWP anddeactivate the third BWP. The base station may send, to the wirelessdevice, information indicating that the first BWP is configured as theprimary active BWP of the cell. The wireless device may determine, basedon a value of a field of the DCI, whether to activate the third BWP orto switch from the second BWP to the third BWP. The base station maysend, to the wireless device, a MAC CE associated with a BWP activation.The base station and/or the wireless device may activate or deactivate,based on the MAC CE, each of a plurality of BWPs associated with the MACCE.

A base station and/or a wireless device may activate a first BWP of acell (e.g., as a first active BWP) and a second BWP of the cell (e.g.,as a second active BWP). The base station may send, via the first BWP,DCI comprising a first field and a second field. The first field mayindicate the second BWP and the second field may indicate a first value.Based on the first field indicating the second BWP and on the secondfield indicating the first value, the base station and/or the wirelessdevice may maintain the first BWP as an active BWP and deactivate thesecond BWP. The first BWP may be activated as a primary active BWP. Thesecond BWP may be activated as a secondary active BWP. The base stationmay send, to the wireless device, information indicating that the firstBWP is configured as the primary active BWP of the cell. The basestation may send, via the first BWP, second DCI comprising a third fieldand a fourth field. The third field may indicate a third BWP and thefourth field may indicate a second value. Based on the third fieldindicating the third BWP and the fourth field indicating the secondvalue, the base station and/or the wireless device may switch from thefirst BWP to the third BWP or activate the third BWP while maintainingan active state of the first BWP. The base station may send, to thewireless device, a MAC CE associated with a BWP activation. The wirelessdevice may activate or deactivate, based on the MAC CE, each of aplurality of bandwidth parts (BWPs) associated with the MAC CE.

A wireless device and/or a base station may activate a first BWP of acell and a second BWP of the cell. The cell may comprise a primary cellor a secondary cell. The first BWP may be a primary BWP. The second BWPmay be a secondary BWP. The activating the first BWP and/or the secondBWP may comprise: activating the first BWP at a first time interval,and/or activating the second BWP at a second time interval at leastpartially overlapped with the first time interval. The activating thefirst BWP and the second BWP may comprise activating the second BWPafter the wireless device activates the first BWP. The activating thefirst BWP and the second BWP may comprise activating the first BWPduring a first time interval and activating the second BWP during asecond time interval. The activating the first BWP and the second BWPfurther comprises maintaining and inactive state of the default BWP. Themaintaining an inactive state of the default BWP comprises at least oneof: not monitoring a downlink control channel on the default BWP, notreceiving downlink signals on the default BWP, and/or not transmittinguplink signals on the default BWP. The activating the first BWP maycomprise at least one of: monitoring, on the first BWP, a downlinkcontrol channel on a search space set in a control resource set forreceiving a radio resource assignment, and/or receiving or transmittinga transport block based on the radio resource assignment. The activatingthe second BWP may comprise at least one of: monitoring, on the secondBWP, a downlink control channel on a search space set in a controlresource set for receiving a radio resource assignment, and receiving ortransmitting a transport block based on the radio resource assignment.The base station may send, to the wireless device that may receive, oneor more messages (e.g., a radio resource control message) comprisingconfiguration parameters of the cell. The configuration parameters mayindicate a value of a time period of inactivity. The configurationparameters may indicate: a control resource set of the first BWP, asearch space set of the first BWP, a subcarrier space of the first BWP,a quantity of symbols of the first BWP, and/or a set of resource blocksof the first BWP. The base station may send, to the wireless device thatmay receive, a first downlink signal in a first slot. The wirelessdevice may monitor a downlink control channel on the first BWP fordownlink control information (DCI). The wireless device may switch,based on a time period of inactivity after the first slot, from thefirst BWP to a default BWP of the cell as an active BWP of the cell. Thedefault BWP may be different form the first BWP and/or the second BWP.The time period of inactivity may comprise a duration of time that a BWPinactivity timer is running The time period of inactivity may comprisenot receiving a second downlink signal on the first BWP, and/or nottransmitting uplink signals on the first BWP. The first downlink signalmay comprise at least one of: downlink control information, and/or adownlink transport block. The wireless device may switch from the firstBWP to the default BWP as an active BWP further based on a determinationthat the DCI is not received during the monitoring. The wireless devicemay deactivate, based on the switching from the first BWP to the defaultBWP, the second BWP. The switching from the first BWP to the default BWPmay comprise deactivating the first BWP and/or activating the defaultBWP as the active BWP. The deactivating the first BWP may comprise:stopping monitoring a downlink control channel on the second BWP,stopping receiving downlink signals on the second BWP, and/or stoppingtransmitting uplink signals on the second BWP. The wireless device maydeactivate the first BWP based on or in response to receiving at leastone of: a first command indicating activation of the cell, a secondcommand indicating activation of the first BWP, and/or a third commandindicating switching an active BWP to the first BWP. The command maycomprise at least one of: a radio resource control message, a MAC CE,and/or DCI. The wireless device may deactivate the second BWP based onor in response to receiving at least one: a first command indicatingactivation of the cell, a second command indicating activation of thesecond BWP, and/or a third command indicating switching an active BWP tothe second BWP. The wireless device may switch from the default BWP to athird BWP of the cell as an active BWP. The third BWP and the first BWPmay be the same active BWP of the cell. The wireless device may havemore than one active BWP. The wireless device may start, based onreceiving a second downlink signal via the third BWP, a BWP inactivitytimer. The wireless device may receive, via the third BWP, a thirddownlink signal indicating at least one of: activating a fourth BWP ofthe cell, deactivating the fourth BWP of the cell, switching from thefourth BWP to a fifth BWP as a second active BWP, and/or allocatingradio resources for the fourth BWP. The wireless device may restart,based on the third downlink signal, the BWP inactivity timer.

A wireless device and/or a base station may activate a first bandwidthpart (BWP) of a cell and a second BWP of the cell. The wireless devicemay receive, via the first BWP, a downlink signal via the first BWP atin a first slot. The wireless device may monitor a downlink controlchannel on the first BWP for a downlink control information (DCI). Basedon determining that DCI is not received during a time period (e.g., ofinactivity) after the first slot: switching from the first BWP to adefault BWP of the cell as an active BWP of the cell; and deactivatingthe second BWP. The time period may be associated with a duration oftime that a BWP inactivity timer is running The wireless device mayswitch from the default BWP to a third BWP of the cell as the activeBWP. The wireless device may start, based on receiving a second downlinksignal via the third BWP, a BWP inactivity timer. The wireless devicemay receive, via the third BWP, a third downlink signal indicating atleast one of: activating a fourth BWP of the cell; deactivating thefourth BWP of the cell; switching from the fourth BWP to a fifth BWP asa second active BWP; and/or allocating radio resources for the fourthBWP. The wireless device may restart, based on the third downlinksignal, the BWP inactivity timer. The third BWP and the first BWP may bea same active BWP of the cell. The default BWP may be different from thefirst BWP and the second BWP. The cell may comprise a primary cell or asecondary cell. The first BWP may be a primary BWP. The second BWP maybe a secondary BWP. The switching from the first BWP to the default BWPmay comprise: deactivating the first BWP; and activating the default BWPas the active BWP.

A wireless device and/or a base station may activate a first bandwidthpart (BWP) of a cell as a first active BWP. The wireless device maystart, based on receiving a first downlink signal via the first BWP, aBWP inactivity timer. The wireless device may start the BWP inactivitytimer with an initial timer value based on or in response to receiving afirst downlink signal via the first BWP. The wireless device mayreceive, via the first BWP, a second downlink signal indicating at leastone of: activating a second BWP of the cell/; deactivating the secondBWP of the cell; switching from the second BWP to a third BWP as asecond active BWP; and/or allocating radio resources allocation on forthe second BWP. The wireless device may restart, based on the seconddownlink signal, the BWP inactivity timer. The wireless device mayrestart the BWP inactivity timer with the initial timer value based onor in response to the second downlink signal. The wireless device mayreceive a downlink transport block via the first BWP during a timeperiod, for example, if the BWP inactivity timer is running The wirelessdevice may monitor a downlink control channel on the first BWP fordownlink control information (DCI). The wireless device may switch,based on a determination that the DCI is not received during themonitoring, from the first BWP to a default BWP. The wireless device mayactivate the second BWP of the cell. The wireless device may receive,via the first BWP, a third downlink signal in a first slot. The wirelessdevice may switch, based on a time period of inactivity after the firstslot, from the first BWP to a default BWP of the cell as an active BWPof the cell. The wireless device may deactivate, based on the switchingfrom the first BWP to the default BWP, the second BWP. The wirelessdevice may receive, via the first BWP during a time period that the BWPinactivity timer is running, at least one downlink transport block.

FIG. 50 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 120A and/or 120B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 5000 may include one ormore processors 5001, which may execute instructions stored in therandom access memory (RAM) 5003, the removable media 5004 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive5005. The computing device 5000 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 5001 andany process that requests access to any hardware and/or softwarecomponents of the computing device 5000 (e.g., ROM 5002, RAM 5003, theremovable media 5004, the hard drive 5005, the device controller 5007, anetwork interface 5009, a GPS 5011, a Bluetooth interface 5012, a WiFiinterface 5013, etc.). The computing device 5000 may include one or moreoutput devices, such as the display 5006 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 5007, such as a video processor. There mayalso be one or more user input devices 5008, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device5000 may also include one or more network interfaces, such as a networkinterface 5009, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 5009 may provide aninterface for the computing device 5000 to communicate with a network5010 (e.g., a RAN, or any other network). The network interface 5009 mayinclude a modem (e.g., a cable modem), and the external network 5010 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 5000 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 5011, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 5000.

The example in FIG. 50 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 5000 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 5001, ROM storage 5002, display 5006, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 50.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

1. A method comprising: activating, by a wireless device, a primarybandwidth part (BWP) of a cell and a secondary BWP of the cell; based ona determination that the primary BWP is active, switching from theprimary BWP to a default BWP of the cell as an active BWP of the cell;and based on the switching from the primary BWP to the default BWP andbased on a determination that the secondary BWP is active, deactivatingthe secondary BWP.
 2. The method of claim 1, further comprising:receiving at least one radio resource control (RRC) message indicatingthe default BWP.
 3. The method of claim 1, further comprising: receivingone or more radio resource control (RRC) messages comprising at leastone of: an indication of the primary BWP; and an indication of thesecondary BWP.
 4. The method of claim 1, wherein: the primary BWPcomprises a common search space; and the secondary BWP comprises auser-device specific search space.
 5. The method of claim 1, wherein theswitching is based on a period of inactivity of the primary BWP.
 6. Themethod of claim 5, wherein the period of inactivity comprises at leastone of: a period of inactivity of the primary BWP after receiving adownlink signal in a first slot; a period of time associated with a BWPinactivity timer; or not receiving downlink control information (DCI)before an expiration of the BWP inactivity timer.
 7. The method of claim1, further comprising: monitoring a downlink control channel on theprimary BWP for downlink control information (DCI), wherein theswitching from the primary BWP to the default BWP is based on adetermination that the DCI is not received during the monitoring.
 8. Themethod of claim 1, further comprising: switching from the default BWP toa third BWP of the cell as the active BWP; based on receiving a seconddownlink signal via the third BWP, starting a BWP inactivity timer;receiving, via the third BWP, a third downlink signal indicating atleast one of: activating a fourth BWP of the cell; deactivating thefourth BWP of the cell; switching from the fourth BWP to a fifth BWP asa second secondary BWP; or allocating radio resources for the fourthBWP; and based on the third downlink signal, restarting the BWPinactivity timer.
 9. The method of claim 8, wherein the third BWP andthe primary BWP are a same active BWP of the cell.
 10. The method ofclaim 1, wherein the default BWP is different from the primary BWP andthe secondary BWP.
 11. The method of claim 1, wherein the switching fromthe primary BWP to the default BWP comprises: deactivating the primaryBWP; and activating the default BWP as the active BWP.
 12. The method ofclaim 1, wherein the activating the primary BWP and the secondary BWPcomprises: activating the primary BWP during a first time interval; andactivating the secondary BWP during a second time interval.
 13. Awireless device comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: activate a primary bandwidth part (BWP) of acell and a secondary BWP of the cell; based on a determination that theprimary BWP is active, switch from the primary BWP to a default BWP ofthe cell as an active BWP of the cell; and based on switching from theprimary BWP to the default BWP and based on a determination that thesecondary BWP is active, deactivate the secondary BWP.
 14. The wirelessdevice of claim 13, wherein the instructions, when executed by the oneor more processors, cause the wireless device to: receive at least oneradio resource control (RRC) message indicating the default BWP.
 15. Thewireless device of claim 13, wherein the instructions, when executed bythe one or more processors, cause the wireless device to: receive one ormore radio resource control (RRC) messages comprising at least one of:an indication of the primary BWP; and an indication of the secondaryBWP.
 16. The wireless device of claim 13, wherein: the primary BWPcomprises a common search space; and the secondary BWP comprises auser-device specific search space.
 17. The wireless device of claim 13,wherein the switching is based on a period of inactivity of the primaryBWP.
 18. The wireless device of claim 17, wherein the period ofinactivity comprises at least one of: a period of inactivity of thefirst BWP after receiving a downlink signal in a first slot; a period oftime associated with a BWP inactivity timer; or not receiving downlinkcontrol information (DCI) before an expiration of the BWP inactivitytimer.
 19. The wireless device of claim 13, wherein the instructions,when executed by the one or more processors, cause the wireless deviceto: monitor a downlink control channel on the primary BWP for downlinkcontrol information (DCI), wherein the switching from the primary BWP tothe default BWP is based on a determination that the DCI is not receivedduring the monitoring.
 20. The wireless device of claim 13, wherein theinstructions, when executed by the one or more processors, cause thewireless device to: switch from the default BWP to a third BWP of thecell as the active BWP; based on receiving a second downlink signal viathe third BWP, start a BWP inactivity timer; receive, via the third BWP,a third downlink signal indicating at least one of: activating a fourthBWP of the cell; deactivating the fourth BWP of the cell; switching fromthe fourth BWP to a fifth BWP as a second secondary BWP; or allocatingradio resources for the fourth BWP; and based on the third downlinksignal, restart the BWP inactivity timer.
 21. The wireless device ofclaim 20, wherein the third BWP and the primary BWP are a same activeBWP of the cell.
 22. The wireless device of claim 13, wherein thedefault BWP is different from the primary BWP and the secondary BWP. 23.The wireless device of claim 13, wherein the instructions to switch fromthe primary BWP to the default BWP cause the wireless device to:deactivate the primary BWP; and activate the default BWP as the activeBWP.
 24. The wireless device of claim 13, wherein the instructions, whenexecuted by the one or more processors, cause the wireless device to:activating the primary BWP during a first time interval; and activatingthe secondary BWP during a second time interval.
 25. A non-transitorycomputer-readable medium comprising instructions that, when executed,configure a wireless device to: activate a primary bandwidth part (BWP)of a cell and a secondary BWP of the cell; based on a determination thatthe primary BWP is active, switch from the primary BWP to a default BWPof the cell as an active BWP of the cell; and based on switching fromthe primary BWP to the default BWP and based on a determination that thesecondary BWP is active, deactivate the secondary BWP.
 26. Thenon-transitory computer-readable medium of claim 25, wherein theinstructions, when executed, configure the wireless device to: receiveat least one radio resource control (RRC) message indicating the defaultBWP.
 27. The non-transitory computer-readable medium of claim 25,wherein the instructions, when executed, configure the wireless deviceto: receive one or more radio resource control (RRC) messages comprisingat least one of: an indication of the primary BWP; and an indication ofthe secondary BWP.
 28. The non-transitory computer-readable medium ofclaim 25, wherein: the primary BWP comprises a common search space; andthe secondary BWP comprises a user-device specific search space.
 29. Thenon-transitory computer-readable medium of claim 25, wherein theswitching is based on a period of inactivity of the primary BWP.
 30. Thenon-transitory computer-readable medium of claim 29, wherein the periodof inactivity comprises at least one of: a period of inactivity of thefirst BWP after receiving a downlink signal in a first slot; a period oftime associated with a BWP inactivity timer; or not receiving downlinkcontrol information (DCI) before an expiration of the BWP inactivitytimer.
 31. The non-transitory computer-readable medium of claim 25,wherein the instructions, when executed, configure the wireless deviceto: monitor a downlink control channel on the primary BWP for downlinkcontrol information (DCI), wherein the switching from the primary BWP tothe default BWP is based on a determination that the DCI is not receivedduring the monitoring.
 32. The non-transitory computer-readable mediumof claim 25, wherein the instructions, when executed, configure thewireless device to: switch from the default BWP to a third BWP of thecell as the active BWP; based on receiving a second downlink signal viathe third BWP, start a BWP inactivity timer; receive, via the third BWP,a third downlink signal indicating at least one of: activating a fourthBWP of the cell; deactivating the fourth BWP of the cell; switching fromthe fourth BWP to a fifth BWP as a second secondary BWP; or allocatingradio resources for the fourth BWP; and based on the third downlinksignal, restart the BWP inactivity timer.
 33. The non-transitorycomputer-readable medium of claim 32, wherein the third BWP and theprimary BWP are a same active BWP of the cell.
 34. The non-transitorycomputer-readable medium of claim 25, wherein the default BWP isdifferent from the primary BWP and the secondary BWP.
 35. Thenon-transitory computer-readable medium of claim 25, wherein theinstructions to switch from the primary BWP to the default BWP configurethe wireless device to: deactivate the primary BWP; and activate thedefault BWP as the active BWP.
 36. The non-transitory computer-readablemedium of claim 25, wherein the instructions, when executed, configurethe wireless device to: activate the primary BWP during a first timeinterval; and activate the secondary BWP during a second time interval.37. A method comprising: activating, by a base station device, a primarybandwidth part (BWP) of a cell and a secondary BWP of the cell; based ona determination that the primary BWP is active, switching, for awireless device, from the primary BWP to a default BWP of the cell as anactive BWP of the cell; and based on the switching from the primary BWPto the default BWP and based on a determination that the secondary BWPis active, deactivating, for the wireless device, the secondary BWP. 38.The method of claim 37, further comprising: sending, to the wirelessdevice, at least one radio resource control (RRC) message indicating thedefault BWP.
 39. The method of claim 37, further comprising: sending, tothe wireless device, one or more radio resource control (RRC) messagescomprising at least one of: an indication of the primary BWP; and anindication of the secondary BWP.
 40. The method of claim 37, wherein:the primary BWP comprises a common search space; and the secondary BWPcomprises a user-device specific search space.
 41. The method of claim37, wherein the switching is based on a period of inactivity of theprimary BWP.
 42. The method of claim 37, wherein the default BWP isdifferent from the primary BWP and the secondary BWP.
 43. The method ofclaim 37, wherein the activating the primary BWP and the secondary BWPcomprises: activating the primary BWP during a first time interval; andactivating the secondary BWP during a second time interval.